Lighter Reopens Withdrawals After Returning 5 Million USDC to Drained Trader
Lighter returns 5 million USDC and lifts its emergency pause
About 5 million USDC, a US dollar stablecoin, is back with a trader whose accounts on the perpetual futures exchange Lighter were drained Monday morning. After the money reached the trader, Lighter reopened withdrawals, ending an emergency pause it had put in place during the incident.
In a post-mortem on X, Lighter said the trader's own signing setup, which did not use Lighter's official software development kits (SDKs), exposed the trader's API keys — the credentials that sign an account's transactions. Earlier Monday, Lighter had blamed a leaked API key and said its smart contracts were not hit.
Key points
- Roughly 5 million USDC was returned to the trader, and withdrawals are flowing again.
- Lighter says the trader's custom signing code reused a number that should be unique, which let an attacker work out the API key.
- Lighter's Guardian safeguard froze withdrawals during the incident, allowing the Security Council to return the funds.
- Lighter has added new protections and plans more limits on what API keys can do.
- A researcher estimated about $15.5 million was taken in total, a figure Lighter has not confirmed.
What Lighter's official posts say
Lighter said on X that "deposits and withdrawals are back to normal following the deactivation of Guardian Mode by the Lighter Security Council." The post-mortem added that queued withdrawals are going through.
Lighter said its Guardian, a recently launched smart contract safeguard, caught the anomaly and froze withdrawals, which allowed the Security Council to return the funds. Lighter founder and CEO Vladimir Novakovski said the exchange's escape hatch "provides a safety net in the event of a protocol-wide attack (which this was not, thankfully)."
How the attacker got the key
Every transaction on Lighter, from orders to fund transfers, is signed with an API key. Each signature should carry a fresh random number, called a nonce. Lighter said the trader's code, built outside its official SDKs, repeated nonces. Because signatures are public, two signatures sharing a nonce let the attacker work out the key itself.
A key cannot withdraw to anyone else's wallet. However, Lighter lets a key fund the account's own sub-accounts, and any public pool the account opens — a vault where depositors buy shares and an operator trades for them — falls in that group. Lighter said the attacker opened a pool from the victim's account, used a separate account it controlled to buy pool shares, moved the victim's balance into the pool, then cashed out.
What Lighter is changing
Lighter now requires a wallet signature before funds go into a public pool and has stopped exposing API key signatures. It also plans IP allowlists, per-key limits, and monitoring that voids any key caught reusing a nonce. It told traders unsure of their code to rotate their keys and use an official SDK.
Why this matters for traders using bots
The flaw sat in the trader's own software, so the same risk applies to any account whose signing code mishandles nonces. Lighter noted that nonce reuse breaks signatures on Bitcoin and Ethereum too. The case shows that a custom trading setup, rather than the exchange itself, can be the weak point.
What is confirmed and what is not
Confirmed by Lighter: the return of about 5 million USDC, the reopening of deposits and withdrawals, the role of Guardian Mode and the Security Council, the nonce-reuse explanation, and the new security measures.
Unconfirmed: pseudonymous researcher 0xTria estimated about $15.5 million was taken from two market-maker accounts, $10.39 million and $5.09 million. Lighter has not given a total loss figure and has not confirmed these numbers.