Lighter reopens withdrawals, returns about $5M USDC after trader's API key leak
In brief
- Lighter's Security Council returned about $5 million in USDC to the affected trader, the exchange says.
- Deposits and withdrawals resumed after the council deactivated Guardian Mode, Lighter said.
- Third-party signing software that reused nonces leaked the keys, according to Lighter.
- Onchain analysts estimated losses at $15.5 million; Lighter hasn't confirmed the figure.
How the attack worked
Lighter first reported a suspected compromise involving one external party, and as a precaution it suspended withdrawals and pool creation. It later traced the problem to a leaked API key for one trader's account (and said its priority was recovering funds from an additional withdrawal attempt).
The attacker's method used Lighter's own pool feature. According to Lighter's postmortem, the attacker opened a public pool from the compromised account, then minted shares in a separate account they controlled. They moved the trader's funds into the pool without minting more shares. That pushed up the value of the attacker's shares, which were redeemed before the withdrawal.
Lighter said the anomaly tripped its smart contract Guardian. The Guardian's temporary pause on withdrawals is what gave the Security Council room to return the funds.
"Deposits and withdrawals are back to normal following the deactivation of Guardian Mode by the Lighter Security Council," Lighter announced later that day
A leak through the trader's own signatures
Lighter said the API keys leaked through the account's own signatures. The account used signing software from outside Lighter's official SDKs, and it reused nonces. That's the crux. Per the report, anyone could calculate the private key from two public signatures if both used the same nonce and key.
The exchange said its official SDKs, protocol, smart contracts and infrastructure weren't affected (that's Lighter's own assessment).
It's also changing the rules. Lighter said an API key alone can no longer authorize a transfer to a public pool, it now requires a wallet signature, and it's made API key signatures non-public. The team said it's adding IP allowlists and per-key permissions too, including limits on which markets a key can trade.
What Lighter hasn't disclosed
Lighter didn't disclose the total size of the theft or name the affected trader. Onchain analysts Lookonchain and Onchain Lens estimated the losses at $15.5 million, a figure Lighter hasn't confirmed. The same analysts suggested the account belonged to Abraxas Capital, though Lighter didn't name the trader.
Lighter hasn't said how the roughly $5 million it returned compares with the total.
Frequently asked questions
How did the attacker take funds from the Lighter trader's account?
According to Lighter's postmortem, the attacker opened a public pool from the compromised account and minted shares in a separate account they controlled. They then moved the trader's funds into the pool without minting more shares, which raised the value of the attacker's shares. Those shares were redeemed before the withdrawal.
How did the trader's API keys leak?
Lighter said the keys leaked through the account's own signatures. The account used signing software from outside Lighter's official SDKs and reused nonces. According to the report, anyone could calculate the private key from two public signatures if both used the same nonce and key.
What is Lighter changing after the API key incident?
Lighter said an API key alone can no longer authorize a transfer to a public pool. It now requires a wallet signature and has made API key signatures non-public. The team said it's also adding IP allowlists and per-key permissions, including limits on which markets a key can trade.


