0x7d2d5fec7d2d…7d2d5fe9
Lighter Halts Withdrawals After $10.4 Million USDC Exploit
Lighter froze withdrawals at 6:02 a.m. ET after a wallet drained 10.39 million USDC via a trader's leaked API key; the DEX targets end-of-day Monday to restore withdrawals.

Outputs
A wallet drained 10,393,057 USDC (~$10.4 million) from Lighter's Ethereum contract at 5:11 a.m. ET Monday.
Lighter halted withdrawals and pool creation at 6:02 a.m. ET, 51 minutes after the drain.
A 7:49 a.m. update attributed the incident to one trader's leaked trading API key; Lighter says protocol and smart contracts are unaffected.
Lighter's Security Council will upgrade contracts with Guardian mode enabled, targeting end-of-day Monday for withdrawal restoration.
Lighter runs a decentralized perpetual-futures exchange on its own rollup, with Ethereum handling deposit and withdrawal settlement.
Lighter, a decentralized perpetual-futures exchange, halted all withdrawals Monday after a wallet extracted 10,393,057 USD Coin (USDC) — roughly $10.4 million — from its Ethereum settlement contract.
The drain occurred at 5:11 a.m. ET, according to on-chain records cited in the exchange's own incident notices. Lighter suspended withdrawals 51 minutes later, at 6:02 a.m. ET. The same notice froze pool creation while the team investigated what it described as a suspected compromise involving a single outside party.
An update at 7:49 a.m. ET sharpened the diagnosis. Lighter said the incident stemmed from a leaked trading API key tied to one trader — not from a flaw in its protocol. The exchange stated that the protocol and its smart contracts were unaffected. It did not explain how the key was exposed.
What does the halt actually cover?
Two functions went dark at 6:02 a.m.: withdrawals and the creation of new liquidity pools. Trading infrastructure itself stayed live, per the exchange's framing that the smart contracts remain sound. The operational logic is straightforward — if a credential outside the contract layer has been abused, you choke the exit points first and audit later.
Lighter's architecture matters here. The exchange runs decentralized perpetuals on its own rollup, while Ethereum handles settlement for deposits and withdrawals. That means the $10.4 million left through the Ethereum-side contract, the layer Lighter uses as its bridge to users' funds, even though the trading engine sits on a separate chain.
How does Lighter plan to restore service?
The 7:49 a.m. update laid out a two-part response. First, Lighter's Security Council will upgrade the contracts with Guardian mode enabled — a mechanism that gives designated actors emergency controls during and after the upgrade window. Second, the exchange set an end-of-day Monday target for restoring withdrawals.
That timeline is tight. Contract upgrades coordinated through a Security Council typically involve multisig execution and staged deployment, and doing it under Guardian mode suggests Lighter wants a safety override in place before it reopens fund flows. The exchange has not said whether the affected trader will be made whole, nor whether any funds are recoverable.
Why a leaked API key is a serious failure mode
API keys sit outside the smart-contract perimeter, which is both their appeal and their risk. A trader uses them to automate orders; anyone who obtains one can act with the trader's permissions. Lighter's statement that its contracts are unaffected is technically consistent with a $10.4 million loss — the compromise happened at the credential layer, and the contract did what an authorized key told it to do.
That distinction will shape how the incident is judged. No oracle manipulation, no reentrancy, no bridge exploit — just a key that left a trader's control. The exchange did not disclose whether the key was phished, sold, or leaked through a third-party tooling integration.
The open question is execution. If withdrawals resume by end of day Monday as targeted, Lighter contains the story to one compromised account. If the deadline slips, a $10.4 million drain starts to look like an operational stress test the exchange's rollup-and-settlement design wasn't built to absorb quietly.
via tokenpost.com (Source)
More from Daniel Okafor
Show full bio
Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.
1,514 articles