
Lighter Restores Withdrawals After $5 Million Recovery Following API Key Exploit
Decentralized perpetual exchange Lighter resumed withdrawals after its Security Council returned about $5 million in USDC to an affected trader following a November 16 exploit. The platform attributes the breach to unsafe signing code that reused cryptographic nonces, and has since added wallet-signature requirements for public pool transfers.
Written by CoinArticle’s AI Newsroom · from 2 cited sources. How we work
What Happened
Decentralized perpetual futures exchange Lighter restored withdrawals after its Security Council returned approximately $5 million in USDC to an affected trader, following an exploit on November 16. The platform says the incident began when a trader's API keys were exposed through transaction signing code that was not part of its official software development kits.
According to Lighter's postmortem, the affected code repeatedly reused cryptographic nonces. That allowed an attacker to reconstruct private keys from publicly available signatures. The attacker then used the compromised keys to create a public pool from the victim's account, acquire pool shares through a separate account, move the victim's funds into the pool, and redeem the shares to extract the assets.
Scale of the Losses
The size of the loss is disputed. Blockchain investigators traced approximately $10.4 million in USDC withdrawn from the platform, while other researchers estimated potential losses of $15.5 million across two accounts. Lighter has not confirmed either broader figure. Its confirmed recovery covers roughly $5 million, and the company has not said how much of the remainder, if any, was lost.
The sources also differ on the sequence of the response. Lighter said its Guardian smart contract mechanism was triggered by the suspicious activity, which paused withdrawals and allowed the Security Council to return funds. The Defiant framed the event as an API-key theft, while Crypto Briefing described the earlier step as a temporary suspension of withdrawals and pool creation while the company investigated a suspected exploit involving a compromised external party.
Recovery and Current Status
Lighter said its protocol, smart contracts, infrastructure, and official SDKs were not compromised. Guardian mode has since been disabled, withdrawals have resumed, and pending requests are being processed.
Changes to Security Controls
The exchange has added a requirement for wallet signatures on transfers into public pools and made API key signatures nonpublic, which addresses the mechanism used in the attack. Lighter also plans to introduce IP allowlists, configurable API key permissions, and automated monitoring for nonce reuse.
Traders who use custom or third-party signing software are advised to rotate their API keys and move to Lighter's official SDKs. The exchange's account of the root cause places responsibility on code outside its own SDKs, which is a point traders relying on third-party tooling will need to weigh.
Why It Matters
For Traders
Withdrawals are resuming, but traders using custom or third-party signing tools should rotate API keys now, since the exploit targeted exposed signatures.
For Investors
The gap between Lighter's confirmed recovery and the $10.4 million to $15.5 million loss estimates signals unresolved accounting risk for perpetual exchanges handling delegated trading keys.
For Builders
Any signing code that reuses cryptographic nonces can leak private keys from public signatures, so nonce uniqueness should be enforced and tested in every integration.
This article is for information only and is not financial advice. Read the full disclaimer.






