0x5f0e19d55f0e…5f0e19d2

ConfirmedSecurity589 vB157 sat/vB3 min decode

Lighter Restores Withdrawals After $10.4M USDC Nonce-Reuse Incident

Lighter has resumed deposits and withdrawals after a November 16 nonce-reuse incident traced by Bitquery to a $10.4 million USDC outflow, with about $5 million returned to traders.

Lighter Reopens Withdrawals After Nonce-Reuse Error Exposes Trader API Keys
WitnessLighter Reopens Withdrawals After Nonce-Reuse Error Exposes Trader API Keys3844328 / pixabay

Outputs

  1. Bitquery traced 10,393,057 USDC (~$10.4M) withdrawn from a Lighter-related Ethereum contract on November 16.

  2. Lighter reports roughly $5 million USDC returned to affected traders after deactivating Guardian mode.

  3. Root cause attributed to nonce reuse in unofficial signing code, not a smart-contract exploit.

  4. New controls include wallet signatures for public-pool transfers, IP allowlists, scoped permissions and nonce monitoring.

Decentralized derivatives venue Lighter has resumed deposits and withdrawals following a November 16 security incident that froze account access, with the protocol attributing the failure to unsafe signing code used by affected traders rather than a compromise of its smart contracts.

Blockchain analytics firm Bitquery traced a withdrawal of 10,393,057 USDC — roughly $10.4 million — from a Lighter-related contract on Ethereum on the day of the incident. The funds were converted into ether, and investigators followed part of the subsequent movement through multiple wallets. Lighter, for its part, reports that approximately $5 million USDC has been returned to affected traders. The two figures should not be conflated: the $10.4 million is an observed on-chain outflow, while the $5 million is the venue's own recovery accounting, which may still evolve.

What actually broke?

According to Lighter's reported postmortem, some affected accounts ran unofficial or custom signing code that reused one-time cryptographic values known as nonces. Reusing nonces under the wrong signature scheme can allow an attacker to derive secret signing material from information that was designed to be public. Once an API signing key is compromised in this way, an attacker can issue instructions through normal account capabilities that appear fully authorized.

The distinction matters for how the market reads this incident. Lighter's core protocol software, by the venue's account, behaved as designed. The failure occurred in external client software — a category that smart-contract audits do not and cannot cover.

How the containment unfolded

Lighter activated its Guardian safeguard during the incident, temporarily restricting withdrawals and related activity while its Security Council responded. The venue has since deactivated Guardian mode, and its official announcements channel states that deposits and withdrawals are back to normal, with pending requests being processed.

The recovery remains partial. The observed $10.4 million outflow exceeds the roughly $5 million returned to traders by more than $5 million, and earlier reports cited potentially higher amounts spanning more than one account — figures Lighter had not confirmed. A complete, reconciled loss and recovery report has not yet been published.

What does this change for traders running custom automation?

The operational lesson is specific: audit signing code, rotate any uncertain keys, and understand precisely what each API credential can authorize. Lighter says it has changed how API signatures are exposed and now requires wallet signatures for transfers into public pools. Planned controls include IP allowlists, scoped permissions, per-key limits, and automated monitoring for repeated nonces.

Nonce-reuse vulnerabilities deserve particular attention because digital signatures depend on the uniqueness and secrecy of temporary values. If an attacker infers a private key from flawed signatures, restarting an interface or changing a password does not repair the exposed credential. The practical scope depends on which keys were affected and whether they could authorize actions beyond trading. Users should follow the protocol team's specific revocation and key-rotation instructions rather than treating the reopening of withdrawals as the end of every associated risk.

The accounting that remains open

This is now a restoration-and-root-cause story rather than a withdrawal-halt headline. The outstanding questions are quantifiable: a full reconciliation of losses against recovered funds, confirmation of whether the initial outflow exceeds the observed $10.4 million, and evidence that the new permissioning and nonce-monitoring controls hold under live trading volume. Until Lighter or an independent investigator publishes that reconciled report, the gap between $10.4 million observed and $5 million returned is the number practitioners should track.

via newsbtc.com (Source)

More from Nathan Brooks

Nathan Brooks

Show full bio

Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,512 articles