0x625d69be625d…625d69c1
Lighter Restores Withdrawals After $5M Recovery From API Key Exploit
Lighter recovered $5M in USDC after a nonce-reuse flaw in third-party signing code exposed a trader's API keys; Guardian contracts paused the drain.

Outputs
Lighter recovered approximately $5 million in USDC and resumed withdrawals after the November 16 exploit.
Investigators traced roughly $10.4 million in USDC outflows; other researchers estimated $15.5 million in losses across two accounts.
The flaw came from non-SDK signing code reusing cryptographic nonces, letting an attacker reconstruct private keys.
Guardian smart contracts auto-paused withdrawals, enabling the Security Council to return $5 million to the trader.
New protections include required wallet signatures for pool transfers, nonpublic API signatures, and planned nonce-reuse monitoring.
Decentralized perpetual futures exchange Lighter resumed withdrawals on November 18 after recovering approximately $5 million in USDC from a November 16 exploit that compromised a trader's API keys through unsafe transaction signing, according to the platform's postmortem report.
The root cause sat outside Lighter's own code. The affected accounts ran signing software not built on the exchange's official software development kits, and that code repeatedly reused cryptographic nonces. Reused nonces let an attacker reconstruct private keys from publicly available signatures, the postmortem explained.
How did the attacker move the funds?
The attacker used the compromised keys to execute a four-step extraction through Lighter's own market structure:
- Created a public pool from the affected account
- Acquired pool shares through a separate attacker-controlled account
- Transferred the victim's funds into that pool
- Redeemed the shares to extract the assets
Lighter detected the suspicious activity through its Guardian smart contract mechanism, which triggered automatically. Guardian mode paused withdrawals and pool creation, giving the exchange's Security Council time to return roughly $5 million in USDC to the affected trader. The platform has since disabled Guardian mode, reopened withdrawals, and begun processing the queued requests that accumulated during the suspension.
The confirmed recovery covers only part of the suspected outflow. 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 those broader figures, and the postmortem did not reconcile them against the $5 million recovery.
What was and was not compromised?
Lighter stated that its protocol, smart contracts, infrastructure, and official SDKs were not breached. The failure occurred in third-party or custom signing tooling that misused nonce generation, a cryptographic hygiene issue comparable to the 2013 Android Bitcoin wallet flaw that leaked private keys through repeated nonce values.
The exchange has already shipped two mitigations: wallet signatures are now required for transfers into public pools, and API key signatures have been made nonpublic. Three further controls are on the roadmap:
- IP allowlists for API access
- Configurable API key permissions
- Automated monitoring for nonce reuse
Lighter advised any trader using custom or third-party signing software to rotate their API keys immediately and migrate to the official SDKs. That guidance carries operational weight for algorithmic and high-frequency traders, who are the most likely group to run bespoke signing infrastructure rather than packaged tooling.
What happens next?
The immediate containment window has closed, but two questions remain open. Lighter has not stated whether the gap between the confirmed $5 million recovery and the $10.4 million to $15.5 million in researcher-estimated outflows will be addressed, and the postmortem did not name the external signing software involved. The effectiveness of the new nonce-reuse monitoring and IP allowlists, which Lighter has promised but not yet dated, will determine whether this class of key-exposure attack stays closed.
via Crypto Briefing (Source)
More from Tom Whitfield
Show full bio
News editor covering technology and product news in crypto and web3 industry at Mempool Brief.
1,374 articles