0x075b74c2075b…075b74c5
Lighter Restores Withdrawals and Returns $5 Million in USDC After Exploit
Lighter returned about $5 million in USDC to users exploited via nonce reuse in unofficial signing code, restarted withdrawals, and mandated wallet signatures for public-pool transfers.

Outputs
Lighter returned about $5 million in USDC to users affected by a Nov. 16 incident.
Attackers derived API private keys by exploiting repeated nonce reuse in accounts using unofficial signing code.
The platform's Guardian smart-contract safeguard triggered a temporary withdrawal suspension.
Lighter's protocol, smart contracts, infrastructure and official SDK were not affected.
Wallet signatures are now mandatory for transfers to public pools; IP allowlists and key-revocation monitoring are planned.
Lighter has returned roughly $5 million in USDC to users hit by a Nov. 16 security incident and reopened withdrawals, ending a suspension triggered by the platform's smart-contract Guardian safeguard.
The derivatives platform said attackers exploited trading accounts that used unofficial signing code rather than its official SDK. The technical root: repeated use of a nonce — the number embedded in a digital signature — let attackers derive API private keys from public signatures.
How did the attackers move the funds?
Once they held the keys, accounts controlled by the attackers created a public pool on the platform, transferred victim funds into it, and redeemed pool shares to extract the assets. That chain of actions is what tripped Lighter's Guardian safeguard, a smart-contract-level protection that prompted a temporary withdrawal suspension across the platform.
Lighter was direct about the blast radius. Its protocol, smart contracts, infrastructure and official SDK were not affected, the platform said. The exposure was confined to accounts where users had adopted third-party signing implementations that mishandled nonces.
What has been made whole?
The platform's Security Committee has already returned about $5 million in USDC to affected traders. Withdrawals are live again, and pending withdrawal requests from the suspension window are being processed.
That turnaround matters operationally. A withdrawal pause on a trading venue, even a short one, freezes working capital for active traders and market makers. Restoring access within days — and covering user losses from committee-controlled funds rather than leaving victims to absorb them — limits the reputational and liquidity damage that has followed similar incidents at other venues.
What changed to stop a repeat?
Lighter has already shipped two fixes. Wallet signatures are now mandatory for any transfer to a public pool, closing the redemption route the attackers used. API key signatures are now private, removing the public-signature exposure that made nonce-based key derivation possible.
Three further controls are on the roadmap:
- IP allowlists for API access
- Granular API key permissions and limits
- Monitoring designed to revoke keys at risk of nonce reuse before they can be exploited
The last item is the most consequential. Detecting nonce reuse in real time — rather than after keys are compromised — would shift the platform from incident response to prevention. No timeline was given for those additions.
For users, the immediate lesson is narrower: unofficial signing tooling sat outside Lighter's audited surface, and the platform's clean bill of health for its official SDK doesn't extend to third-party integrations. Whether the upcoming permission system will formally restrict or flag unofficial clients remains to be seen as Lighter rolls out the changes.
via tokenpost.com (Source)
More from Daniel Okafor
Show full bio
Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.
1,514 articles