For builders using Lighter’s API, the key distinction in its November 16 security incident is between signing code and the protocol itself. In a report covered on November 18, 2026, Lighter said a trader used non-official signing code that reused a signature nonce—a value that should not be reused. According to Lighter, this exposed the trader’s API key, after which an attacker transferred funds.
Lighter said its protocol, smart contracts, infrastructure and official SDK were not affected. The unusual activity triggered the smart contract’s Guardian protection, temporarily pausing withdrawals. Lighter said its security committee was then able to return approximately 5 million USDC to the affected trader. Withdrawals have resumed, with backlogged requests still being processed.
Lighter has since required a wallet signature for transfers to the public pool. It also plans to add IP allowlisting, configurable permissions and limits for API keys; those API-key controls were planned, not described as already in place.