Skip to content
Advertisement
Lighter resumes withdrawals after recovering $5 million following API key exploit

Lighter resumes withdrawals after recovering $5 million following API key exploit

lighter logo banner

The decentralized exchange traced the incident to unsafe signing code that exposed a trader’s API keys, allowing an attacker to move funds through a public pool.

Decentralized perpetual futures exchange Lighter has restored withdrawals after recovering approximately $5 million in USDC following a security exploit on November 16 that exposed a trader’s API keys through unsafe transaction signing.

In a postmortem report, Lighter said the affected accounts used signing code outside its official software development kits that repeatedly reused cryptographic nonces, allowing an attacker to reconstruct private keys from publicly available signatures.

The attacker used the compromised keys to create a public pool from the affected account, acquire pool shares through a separate account, transfer the victim’s funds into the pool, and redeem the shares to extract the assets.

Advertisement

The incident prompted Lighter to temporarily suspend withdrawals and pool creation earlier Monday as it investigated a suspected exploit involving a compromised external party.

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 loss estimates.

Lighter said its Guardian smart contract mechanism was triggered by the suspicious activity, temporarily pausing withdrawals and allowing its Security Council to return approximately $5 million in USDC to the affected trader.

The exchange confirmed that 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.

Lighter has implemented additional protections requiring wallet signatures for transfers into public pools and making API key signatures nonpublic. The platform also plans to introduce IP allowlists, configurable API key permissions, and automated monitoring for nonce reuse.

The exchange advised traders using custom or third party signing software to rotate their API keys and switch to its official SDKs.

Disclosure: This article was edited by John Chen. For more information on how we create and review content, see our Editorial Policy.