Summary

  • Lighter resumed deposits and withdrawals on November 16 2026 after a nonce-reuse incident exposed trader API keys.
  • The lighter incident enabled one wallet to withdraw 10.39 million USDC, which was later swapped to ETH on CoW Swap.
  • Lighter returned about 5 million USDC to the affected trader following the api key theft.

Lighter paused deposits and withdrawals after a nonce-reuse error in its custom signing code. The bug exposed trader API keys. An attacker used them to derive private keys and drain roughly 10.39 million USDC from the platform.

The breach fits a pattern of DeFi security failures.

Traders faced immediate unauthorized transfers. The venue worked to restore services.

Context

Nonce reuse remains a persistent risk in DeFi platforms. These platforms rely on custom code for API authentication instead of standard libraries. The error lets attackers recover private keys when the same nonce appears across multiple signatures. It turns a cryptographic flaw into full account control.

This Lighter incident occurred against ongoing industry efforts to strengthen DeFi security.

Related work on Aave v4 architecture was scheduled for discussion at the DeFi Security Summit in early November 2026.

Details

GoPlusSecurity reported that the attack targeted accounts where reused nonces in custom signing code permitted private-key recovery. One wallet executed the 10.39 million USDC withdrawal on November 16 before routing the funds through CoW Swap.

Lighter returned approximately 5 million USDC to the affected trader once the breach was contained. The platform confirmed that the root cause was isolated to its signing implementation.

"Nonce Reuse in Custom Signing Code Enabled API Private Key Recovery."

, GoPlusSecurity (x.com)

The episode underscores how nonce reuse can bypass even audited environments when teams build their own cryptographic helpers. Affected traders lost access to funds until partial restitution occurred. The wider market watched for signs of similar implementation gaps elsewhere.

Outlook

Platforms will continue to face pressure to replace custom signing routines with vetted libraries. They must expand audit coverage specifically to nonce handling and key derivation paths.