Crime•

$15.48 Million Drained From Two Market Makers Forces Lighter to Freeze Withdrawals

Lighter halted withdrawals and pool creation after about $15.48 million in USDC was drained from two market-maker accounts, apparently through leaked API keys rather than a protocol flaw.

Written By :MINRK
$15.48 Million Drained From Two Market Makers Forces Lighter to Freeze Withdrawals

Photo by max im on Unsplash

Mentioned in This Article

USDC
USDC
USDC
$1.00
0.01%
L
LIT
Price unavailable

1. Lighter exploit: what happened on November 16

Lighter, the perpetual futures exchange built on its own zero-knowledge rollup on Ethereum, froze all withdrawals and new liquidity pool creation on November 16, 2026, after roughly $15.48 million in USDC was drained from two market-maker accounts. The company says the Lighter exploit appears to trace back to a single compromised external party rather than a defect in its protocol.

The suspension was presented as a precaution. In a public statement posted to its official account, the team said it was "actively investigating a security incident that appears to involve a single compromised external party," and that the freeze on withdrawals and pool creation would stay in place while it works out the full extent of the damage.

No date has been given for when withdrawals will reopen. Trading itself was not halted: users could still open and close perpetual positions, but they could not move funds off the platform while the review continued.

2. How much was taken, and from whom?

The suspected loss totals about $15.48 million in USDC, split across two accounts operated by market makers. One account lost approximately $10.39 million, and the second lost approximately $5.09 million. Both belonged to professional liquidity providers rather than ordinary retail traders.

That distinction matters for understanding the scale of the event. Market makers on an exchange like Lighter keep large balances on the platform so they can quote prices continuously on both sides of the order book. Their accounts therefore hold more capital than a typical user account, which makes them attractive targets for anyone who gains a way to control them.

The figure of roughly $15.5 million was the estimate at the time the incident became public. Because the investigation is still open, the final number could be revised once the company completes its assessment.

Losses concentrated in market-maker accounts can also ripple outward to other traders. When liquidity providers are forced to step back, order books tend to thin out, spreads widen and large orders move prices more than usual. Even users whose own balances were untouched can therefore feel the effects of an incident like this one through worse execution while the affected firms regroup.

3. How did the attack on the market-maker accounts work?

The working theory is that the attacker obtained the application programming interface (API) keys tied to the two market-maker accounts and then used a legitimate exchange feature, public liquidity pools, to move the money out. Onchain analyst MLM was among the first to flag the unusual activity, and Tria, the founder of Predicts.guru, later argued that leaked API keys rather than a smart contract flaw were the likely entry point.

API keys are the credentials that trading firms use to connect automated systems to an exchange. They typically allow software to place and cancel orders at high speed without a human approving each action. On Lighter, the keys alone are not supposed to be able to send funds directly to an outside wallet. However, transfers between accounts registered under the same Ethereum mainnet address do not require an additional signature, and a pool created by an account is treated as belonging to that account. Those two properties appear to have given the attacker a path to the money.

The sequence, as reconstructed from onchain data, unfolded in several steps. First, the attacker closed the open trading positions held by the victim accounts. Closing positions released the margin that had been tied up in those trades, turning it into free USDC balance that could be moved.

Next, the attacker set up a public liquidity pool that charged zero fees and bought almost the entire share supply of that pool for roughly $10,000, giving the attacker about 99.99% ownership. With control of the pool established, the victims' USDC was shifted into it in tranches of about $1 million each. Because the attacker owned nearly all of the pool's shares, redeeming those shares let the attacker claim almost all of the deposited capital.

Finally, the redeemed funds were withdrawn and swapped through CoW Protocol, a decentralized trading service that batches orders and settles them onchain. The use of a decentralized venue for the swaps meant there was no central operator positioned to block the trades as they happened.

4. Why Lighter paused pool creation as well as withdrawals

The decision to freeze new pool creation alongside withdrawals follows directly from the method described above. The attacker did not need to break any cryptography or find a coding error; the pool feature itself served as the conduit for moving funds out of the compromised accounts. Leaving that feature open while the investigation ran could have allowed the same technique to be repeated against any other account whose credentials had been exposed.

Halting withdrawals, meanwhile, prevents any further value from leaving the exchange while the team identifies which accounts, if any, remain at risk. Together, the two measures close both the entry route and the exit route used in the attack.

Keeping trading live is a deliberate balancing act. Shutting down the order book entirely would have left every trader unable to manage leveraged positions during a volatile period, potentially causing far wider losses through forced liquidations. By allowing positions to be opened and closed while keeping funds on the platform, Lighter limited the disruption to activity that could not otherwise be safely controlled.

5. What Lighter is and how its exchange is built

Lighter is a decentralized exchange focused on perpetual futures, which are leveraged contracts that let traders bet on the price of an asset going up or down without an expiry date. Unlike traditional futures, perpetuals stay open indefinitely, with periodic funding payments between long and short traders keeping the contract price close to the underlying market.

The platform runs a central limit order book, the same matching structure used by conventional stock and crypto exchanges, rather than the automated market maker model common across decentralized finance. It operates on its own zero-knowledge rollup on Ethereum, which uses cryptographic proofs to make order matching and liquidations verifiable onchain while aiming to deliver the speed traders expect from centralized venues.

Lighter was founded by Vladimir Novakovski. The company raised $68 million in a funding round that valued it at $1.5 billion, making it one of the more prominent new entrants in the decentralized derivatives market. Its native token trades under the ticker LIT.

6. LIT price reaction

The LIT token sold off as news of the incident spread, falling more than 7% as holders reacted to the withdrawal freeze and the size of the loss. The decline reflected uncertainty over how long funds would remain locked and whether the damage was fully contained to the two accounts identified so far.

Exchange tokens are particularly sensitive to security events because their value is closely tied to confidence in the platform's operations. A freeze on withdrawals, even a precautionary one, tends to raise questions among users about access to their capital, which can translate quickly into selling pressure on the associated token.

7. A key management failure, not a smart contract bug

If Lighter's preliminary assessment holds, the weak point was the handling of credentials linked to an external party, not a flaw in the exchange's code. That places the incident in a different category from many decentralized finance exploits, where attackers find errors in smart contract logic and use them to drain pools directly.

For users, the difference is meaningful. A protocol-level bug can put every account on a platform at risk simultaneously, while a credential compromise is usually limited to the accounts whose keys were exposed. Lighter's statement that a single external party was involved points toward the narrower scenario, although the company has not yet published a full post-incident report confirming it.

The episode nonetheless highlights a structural tension that many trading platforms face. Features designed to make life easier for professional users, such as convenient transfers between linked accounts and permissionless pool creation, can become liabilities when the credentials controlling those accounts fall into the wrong hands. The attack did not require any single feature to malfunction; it combined several that were each working as intended.

Market makers, for their part, are likely to scrutinize how their own API keys are stored, rotated and restricted. Credentials that grant broad permissions to automated systems are a common target, and an incident of this size tends to prompt trading firms across the industry to review their internal security practices.

8. What comes next for Lighter users

The immediate questions are how quickly withdrawals resume and whether the investigation confirms that the compromise was confined to one external party and the two affected accounts. Lighter has not provided a timeline for restoring withdrawals or pool creation, and the review remains ongoing.

Users with funds on the platform can still trade but cannot move their balances off the exchange until the freeze lifts. A detailed account of the root cause, any changes to how API keys and inter-account transfers are handled, and a statement on how the affected market makers will be treated are the main pieces of information the market is waiting for.

Until those answers arrive, the incident stands as one of the larger security events of the month in decentralized derivatives trading, and a test of how a fast-growing exchange communicates and recovers under pressure.

How Lighter handles the recovery process, including the speed and transparency of its updates, is likely to weigh on whether traders and liquidity providers return in full once withdrawals reopen. Exchanges that publish clear post-incident reports and concrete fixes have generally been better placed to rebuild trust than those that leave questions unanswered for long periods.

Related Articles

NEWSLETTERS

Don't miss another story.

Subscribe to the MINRK Newsletter today.

Tick the newsletters you want. No selection? You'll get MINRK Headlines.

By signing up, you will receive emails about MINRK products and you agree to our terms of use and privacy policy.

MINRK Daybook

Market analysis for crypto traders and investors.

EVERY WEEKDAY

MINRK for Advisors

Defining crypto, digital assets and the future of finance for financial advisors.

EVERY THURSDAY

MINRK Protocol

Exploring the tech behind crypto one block at a time.

WEEKLY

MINRK Long & Short

A must read for institutions. Insights, news and analysis delivered weekly.

EVERY WEDNESDAY

MINRK Headlines

The biggest crypto news and ideas of the day.

EVERY WEEKDAY

MINRK Policy

Examining the intersection of cryptocurrency and government.

WEEKLY

MINRK Research

Join thousands of readers who rely on MINRK for data-driven insights on the latest digital asset trends.

MONTHLY