lighter api key exploit: $10.4M Drained, $5M Recovered After Nonce Bug
The lighter api key exploit drained about $10.4M in USDC from a market maker on perp DEX Lighter; withdrawals were paused, then restored after roughly $5M was recovered.

- Bitquery traced 10,393,057 USDC leaving Lighter's Ethereum contract at 10:11 UTC on Nov 16, most of it swapped to ETH within minutes.
- Lighter's postmortem says the keys leaked through a trader's custom signing software that reused cryptographic nonces.
- The LIT token fell more than 10% to under $2.48 before recovering to about $2.62, per CoinDesk.
in this block
The lighter api key exploit is Monday's reminder that "the smart contracts are fine" does not mean your funds are. Perp DEX Lighter paused withdrawals after an attacker used a market maker's leaked trading keys to pull about $10.4 million in USDC, then restored them hours later after clawing back roughly $5 million, according to CoinDesk and Cointelegraph.
What actually happened
On Monday morning UTC, Lighter flipped on what it calls Guardian mode, pausing withdrawals and new pool creation while its Security Council investigated. The exchange said early on that its protocol and smart contracts were not compromised and pointed to a leaked API key belonging to a specific trader.
The postmortem, published Monday at 18:20 UTC according to Cointelegraph, filled in the details. The trader's own signing software reused nonces, which allowed the attacker to calculate the private API keys from publicly available signatures. With those keys, the attacker created a public pool, moved the trader's funds into it and withdrew them through an account they controlled.
Guardian mode bought time. Lighter said its Security Council was able to return about $5 million in USDC to the affected trader, and withdrawals were restored later on Monday.
The bug was not in Lighter's contracts. It was in one trader's homemade signing code, and that was enough.
Where the money went
Onchain sleuths were fast. Bitquery said most of the roughly $10.39 million was converted into ETH through CoW Swap. It later identified 1,920 ETH moved through 12 wallets, each receiving 160 ETH, before being routed via LI.FI toward Hyperliquid, where those accounts bought about $3.46 million of XMR1, a token named after Monero. Another 3,845 ETH, about $7 million, still sat in the original wallet as of Bitquery's 11:55 UTC snapshot.
Bubblemaps flagged the same attacker address. CoinDesk noted that other researchers estimated potential losses up to $15.5 million across two market-maker accounts, but Lighter has not confirmed that figure or a second successful withdrawal.
Bitquery also spotted similar routing after a separate $6.45 million Safe wallet theft about 84 minutes later and a Kava exploit two days earlier. It stressed that matching routes are weak evidence of a single attacker. For background on that Kava incident, see our kava lend hack report.
What Lighter is changing
The fixes target exactly how the lighter api key exploit worked. According to Cointelegraph's summary of the postmortem, Lighter now requires wallet signatures for transfers into public pools and has made API-key signatures non-public. It also plans IP allowlists and configurable permissions for API keys.
That is the right direction. API keys are the plumbing of every serious trading desk, and on a DEX they can be just as dangerous as on a centralized exchange. The year has already been loud on this front, from the record binance 6.3b hack in October to a string of smaller drains this month.
Why "contracts unaffected" still hurts
Lighter's message that its smart contracts were safe is accurate, and it matters for the protocol. It does not help the market maker who lost funds, and it does not stop the token from dropping. CoinDesk noted LIT was still about 9% lower over 24 hours even after it bounced.
The episode also shows how much power a security council and an emergency "Guardian" switch hold on a DEX. Pausing withdrawals saved about $5 million here. The same lever could freeze honest users in another scenario, so it is worth knowing who controls it on any venue you use.
For traders, the takeaway is simple: decentralization of the contracts does not remove the risks that come from keys, bots and integrations around them.
What to do as a reader
You probably are not running custom signing code. Still, the lighter api key exploit has lessons for anyone who trades through bots, APIs or third-party tools.
- Treat API keys like private keys. Scope them tightly, rotate them, and never paste them into tools you have not audited.
- Use IP allowlists and permission limits wherever a venue offers them, and turn off withdrawal rights you do not need.
- Check the official Lighter postmortem coverage and Lighter's own channels before believing loss figures from random accounts.
- Be skeptical of "recovery" offers in replies and DMs; exploits attract scammers like moths.
Protocol security is only as strong as the weakest integration. Stay paranoid, ser. Not financial advice.
Not financial advice. DYOR, ser.