Lighter’s November 16 incident: reused signing nonce exposed an API key

A signing-code error, rather than a smart-contract failure, was at the center of Lighter’s November 16 security incident. In a recap reported on November 18, 2026, Lighter said a trader used unofficial signing code that reused a signing nonce—a value intended for a single signature. This exposed the trader’s API key, after which an attacker transferred funds out.

Lighter said its protocol, smart contracts, infrastructure and official SDK were unaffected. The unusual activity triggered the smart contract’s Guardian protection mechanism, temporarily pausing withdrawals. According to Lighter, its security committee was then able to return approximately 5 million USDC to the affected trader. Withdrawals have since resumed, and the platform is processing a backlog of requests.

For builders using the platform, the distinction is between a protection already triggered and controls at different stages of rollout. Lighter said it now requires a wallet signature for transfers to the public pool. IP allowlisting, configurable permissions and limits for API keys remain planned.

Further reading