Lighter resumes withdrawals after nonce-reuse error, returns $5M to traders
TL;DR
- Lighter resumed deposits and withdrawals after its November 16 incident.
- Bitquery observed an approximately 10.4 million USDC withdrawal; Lighter reports about 5 million USDC returned to traders.
- Root cause reported as nonce reuse in unofficial signing code, not a confirmed smart-contract exploit.
Decentralized derivatives venue Lighter restored access after a November 16 security incident. The venue cites unsafe external signing code used by some trader accounts as the cause, distinguishing it from a protocol smart-contract compromise. A cryptographic error in third-party integrations can expose account authority even when core contracts operate as designed.
The on-chain withdrawal was substantial
Bitquery traced 10,393,057 USDC withdrawn from a Lighter-related Ethereum contract on November 16. The funds were converted to ether and moved across multiple wallets. The trace documents an approximate 10.4 million USDC outflow but does not establish a final loss figure. Earlier higher estimates referenced multiple accounts, which Lighter had not confirmed. Recovery accounting may change as details are reconciled.
Why nonce reuse can reveal a key
Lighter’s postmortem reports that some affected accounts used unofficial or custom signing code that reused one-time values, nonces. With certain signature schemes, nonce reuse enables derivation of the private signing key from public signature data. Once an API signing key is exposed, an attacker can issue instructions that appear authorized. This reflects cryptographic key exposure through unsafe client code and highlights the need to use well-tested official signing libraries in trading integrations.
Related context: the Unocoin wallet incident.
The pause and partial recovery
Lighter activated its Guardian safeguard during the incident, restricting withdrawals while its Security Council acted. The venue reports roughly 5 million USDC returned to affected traders and deactivated Guardian mode afterward. It states that deposits and withdrawals have resumed and pending requests are processing. The 5 million USDC recovery does not equal the separately observed 10.4 million USDC outflow. Final exposure requires a reconciled report.
Security changes traders should understand
Lighter changed API signature exposure and now requires wallet signatures for transfers into public pools. Planned additions: IP allowlists, scoped permissions, per-key limits, and monitoring for repeated nonces. Traders using custom automation should audit signing code, rotate uncertain keys, and map each API credential’s authority. Smart-contract audits address protocol risk but do not mitigate insecure key handling in client software.
Nonce-reuse risks are severe because digital signatures require unique, secret ephemeral values. If flawed signatures leak a private key, UI restarts or password changes do not remediate the credential. Impact depends on which keys were affected and what they could authorize. Users should follow the protocol team’s revocation and key-rotation instructions until a full reconciliation confirms scope.
Related context: the Kava Lend exploit.
Current status: restoration in progress and a reported root cause in external signing code. Next required step: a fully reconciled account of losses, recovered funds, and validation of new controls under live trading conditions.
Reporting sources: Lighter official announcements feed · Bitquery transaction investigation · CoinDesk initial incident coverage
Written by the News Desk and edited by Samuel Rae.
Authors credited by the source: NewsBTC Editorial Team
Published by Holder based on an external source.






