Lighter Restores Withdrawals, Returns $5 Million After API Key Leak

Compromised Trading Credentials Expose Public-Pool Transfer Risks as Onchain Loss Estimates Differ
TL;DR
- Lighter restored deposits and withdrawals after a trader's compromised API key was used to move funds through a public pool, with about $5 million in USDC returned to the affected trader.
- Bitquery traced a 10.39 million USDC withdrawal, while Lookonchain and Onchain Lens estimated losses at $15.5 million. Lighter said its protocol and smart contracts were unaffected.
- The exchange introduced mandatory wallet signatures for public-pool transfers and additional API key safeguards following the incident.
Trade smarter on Jupiter, Solana’s leading DEX built for fast execution and deep liquidity.
Swap tokens at competitive rates, route across multiple liquidity sources automatically, and access perpetuals, DCA, and advanced trading tools — all in one place!
Ethereum-based perpetual futures exchange Lighter has reopened deposits and withdrawals following a security incident involving a trader's compromised API key, with its Security Council returning about $5 million in USDC to the affected trader. The exchange said the attacker exploited leaked trading credentials to transfer funds through a public pool, rather than exploiting a vulnerability in its protocol or smart contracts.
Lighter initially reported a suspected compromise involving an external party and temporarily suspended withdrawals and public-pool creation as a precaution. After identifying the leaked API key, the exchange prioritized recovering funds from an additional withdrawal attempt while preparing contract upgrades. Its postmortem explained that an anomaly triggered the platform's smart contract Guardian, activating a temporary withdrawal pause that allowed the Security Council to recover funds. The exchange subsequently disabled Guardian Mode and restored normal operations on Monday.
"Deposits and withdrawals are back to normal following the deactivation of Guardian Mode by the Lighter Security Council," Lighter announced.
How the Attacker Used Lighter's Public Pool System
Lighter's postmortem detailed how the attacker redirected funds without relying on a conventional withdrawal from the compromised account. The attacker first created a public pool using the trader's account and then minted shares in the pool through another account under their control. They subsequently transferred the trader's funds into the pool without issuing additional shares, increasing the value of the shares already held by the attacker. Those shares were then redeemed, allowing the attacker to withdraw the proceeds.
The exchange traced the compromised API keys to signatures generated using signing software outside its official software development kits. According to Lighter, the software reused nonces, which are one-time values used when generating cryptographic signatures. Reusing the same nonce and key across two publicly available signatures made it possible to calculate the private key. Lighter maintained that its official SDKs, protocol, smart contracts and infrastructure were not compromised.
Onchain Investigators Track Larger Losses
Independent blockchain investigators reported different figures associated with the incident. Bitquery identified a specific USDC withdrawal, while Lookonchain and Onchain Lens provided a larger estimated loss figure and suggested that the compromised trading account belonged to Abraxas Capital.
Lighter did not disclose the total amount stolen or identify the affected trader. The investigators' findings therefore remain distinct from the amount the exchange confirmed returning, and the suggested connection to Abraxas Capital has not been established through Lighter's own disclosures.
Lighter Tightens API Key Permissions After Incident
Lighter has changed the authorization requirements governing transfers into public pools. An API key alone can no longer approve those transactions, which now require a wallet signature. The exchange has also made API key signatures non-public to prevent their exposure through the same mechanism involved in the incident. Additional safeguards under development include IP allowlists, configurable permissions for individual API keys and restrictions on the markets each key can trade.
"A key that can trade can still lose you money if someone else holds it," Lighter stated in its postmortem.
This article has been refined and enhanced by ChatGPT.