Lighter exchange halts withdrawals after leaked API key
Lighter exchange halted withdrawals after a leaked trader API key. Bitquery traced $10.39 million in USDC before the pause; about $5 million was later returned.

Lighter exchange halted withdrawals on November 16, 2026, after tying a security incident to a leaked application programming interface (API) key on one trader's account. Bitquery counted 10,393,057 of Circle's USDC leaving the Ethereum settlement contract at 10:11 UTC, and Unchained's check of the same transaction timed it at 10:11:47 UTC and called it $10.39 million, about 51 minutes before the first public halt. The USDC was already moving into Ethereum (ETH) before Guardian mode was public.
Social posts put a second slice near $5.09 million and a combined loss near $15.5 million. Bitquery's window, closed around 12:13 UTC, showed one exit, while Lighter described one trader and later said its Security Council returned about $5 million from a further attempt. The "unaffected" wording means a working contract can still fail one customer, and merging the figures blurs a chain exit, an unconfirmed split and a sum the venue says it returned.
What Lighter exchange posted on the day
At 11:02 UTC Lighter said on X it was "actively investigating a security incident that appears to involve a single compromised external party" and had "temporarily suspended all withdrawals and pool creation." At 12:49 UTC an update said the incident "was caused by a leaked API key for a specific trader's account" and that "The Lighter protocol and smart contracts are unaffected." Guardian mode was on, the priority was "an additional withdrawal attempt by the attacker," and the Security Council would upgrade the contract, with withdrawals still paused, a same-day reopening target and wallet 0xb3fffca23d4444eE73349825ACD84f7b5020e387 named.
At 18:21 UTC Lighter said deposits and withdrawals were "back to normal" after Guardian mode came off, pointing to a postmortem from a minute earlier. CoinMarketCap's account says unofficial signing code reused nonces, so keys could be recovered from public signatures, while official software development kits were unaffected. The attacker opened a public pool, minted shares in another account, moved funds in and redeemed them. The pause let the council return about $5 million in USDC, and the exchange withheld a total for what was taken.
Where Bitquery followed the traced USDC
Within about four minutes the wallet sold roughly 10.36 million USDC on CoW Swap, held 5,764.47 ETH, and sent 1,920 ETH in 12 lots of 160 ETH through LI.FI to Hyperliquid accounts that bought XMR1. At 11:55 UTC Bitquery still saw 3,845 ETH, about $7.0 million. Circle can freeze USDC, and ETH lacks the issuer switch that mattered in the Binance hot-wallet drain. The $5 million return lines up with the 12:49 UTC attempt, rather than with USDC already swapped to ETH before the halt. Lighter has published no reconciliation of the two figures, so the link is a timestamp reading, and Cointelegraph's updated report kept the sums apart.
What the leaked key was allowed to do
Lighter's API-key docs, as DeFi Prime set out that day, let a key trade and withdraw to the Layer 1 (L1) address that created the account, while a transfer to another owner also needs the wallet signature. A pool opened from the affected account can sit inside that same-owner set, so the contracts can follow their rules while the balance leaves, close to the share-mint path that led ACryptoS to deprecate vaults. The pause and restart sit nearer the WAX bridge halt and restart than a hot-wallet breach.
"Our team has been hard at work to help a customer recover 5MM USDC when their API keys were leaked and exploited by an attacker."
Vladimir Novakovski, founder and chief executive of Lighter, posted that at 21:59 UTC on November 16. He called Guardian "key to being able to detect the anomaly and resolve in a way consistent with the verifiable architecture of Lighter." CoinMarketCap showed Lighter's token, LIT, at $2.65, down 6.6% over 24 hours that evening.
What desks should check before the next session
CoinMarketCap's write-up says Lighter now requires a wallet signature before funds enter a public pool and has stopped publishing API-key signatures, with allowlists, per-key limits and nonce checks planned. Watch whether the roughly $5 million shows up apart from ETH already at the named wallet, and whether later USDC moves toward that address. Bitquery's tape ends around 12:13 UTC, before the restart. Rotating keys on Lighter exchange helps only where the new signer stops reusing nonces. Until a failed test shows the controls, the November 16 halt is containment of one account, and the open question is how API authority and public pools interact.
This article is informational analysis only and is not financial, investment, or trading advice. Cryptocurrencies are highly volatile and can lose substantial value rapidly. Past performance and historical patterns do not guarantee future results. Do your own research and consult a regulated financial adviser before making any investment decision.
Reporting by Karthik Subramanian. Filed 17 November 2026, 15:48 GMT.




