UPDATED 21:30 UTC, 16 Nov: Lighter reopened deposits and withdrawals at 18:21 UTC after its Security Council switched off Guardian mode, and says the pause let about $5 million in USDC be returned to the affected trader. Its post-mortem blames signing code outside Lighter’s official SDKs that reused nonces, which let the attacker calculate the trader’s API keys from public signatures. The main attacker wallet still held 3,404.40 ETH at 20:52 UTC. Read our follow-up: Lighter reopens withdrawals, says $5M returned and a reused nonce leaked the key.
SECURITY ALERT
The contracts held, Lighter says.
The key did not.
Lighter, a decentralized exchange for perpetual futures, suspended all withdrawals and new pool creation at 11:02 UTC on Monday after an apparent theft that blockchain analytics firm Bubblemaps puts at about $10.4 million in USDC.
At 12:49 UTC Lighter said its investigation pointed to “a leaked API key for a specific trader’s account”, and that the protocol and its smart contracts were unaffected.
An API key is a credential that lets software trade on an account without the owner’s wallet signing each action.
So how did one trader’s key reach $10 million?
The timeline
Bubblemaps said the attacker deposited about $20,000 into Lighter and withdrew $10.39 million roughly 36 minutes later.
Bitquery traced 10,393,057 USDC leaving Lighter’s Ethereum contract at 10:11 UTC, Cointelegraph reported.
Within four minutes, the USDC was swapped for about 5,764 ETH on CoW Swap, according to Bitquery.
At 11:02 UTC Lighter paused withdrawals, citing “a single compromised external party”.
At 11:58 UTC PeckShield flagged the exploit at about $10 million.
By 12:50 UTC, Bitquery counted twelve payments of 160 ETH, 1,920 ETH in all, routed to Hyperliquid, where twelve accounts held about 6,700 XMR1, a wrapped form of Monero, worth about $3.46 million.
Why Monero?
Follow the funds
Monero is a privacy coin. Once value reaches it, the public trail mostly ends.
Bitquery said 3,845 ETH was still in the main wallet at 12:50 UTC. Our own read of the wallet at 14:42 UTC showed 3,404.55 ETH, about $6.3 million at Kraken’s ether price, by our arithmetic.
Bitquery also flagged a second pair of wallets using the same route with about $6.1 million. It said it had found no direct on-chain link to the Lighter wallet.
Lighter named the main wallet. Bubblemaps published the others. We have not traced them.
Main wallet (named by Lighter): 0xb3fffca23d4444eE73349825ACD84f7b5020e387
XMR1 batch wallets (Bubblemaps): 0x5C239E7607975be5Cf44EC71d2cF1c66d878F746, 0xd8427872a4e9ddf00ee07f02c644447aa6b99926, 0xd1fd67c883466947e1f7dbf06f284cb2785b8c77
How much of the rest can still be stopped?
Lighter’s response
Lighter says it has switched on Guardian mode, a protective setting on its smart contract, and that its Security Council will upgrade the contracts.
Its stated priority is to recover funds tied to “an additional withdrawal attempt by the attacker”. It did not say how large that attempt was.
It aims to finish the upgrades and reopen withdrawals by the end of Monday.
Lighter has not said how the key leaked, what the upgrade changes, or whether the affected trader will be repaid. Cointelegraph, citing Lighter’s documentation, said API keys can move funds between accounts tied to the same wallet, while transfers to a different owner need that owner’s wallet signature.
If a key could not send money to a stranger, how did it get out?
It was Monday’s second incident report. Earlier, Kava put its 14 Nov lending theft at about 53.9 million KAVA.
Protect yourself
- Treat exchange API keys like passwords. Never paste them into bots, browser extensions or shared spreadsheets.
- Give keys the narrowest permissions you need, and revoke any you no longer use, as SignalPlus did with its exchange keys in November.
- If you have funds on Lighter, wait for its own notice before moving them, and ignore direct messages offering “early withdrawal” or recovery help.
Corrections and new evidence: [email protected]
This article is for information only and is not investment advice.
