A signing mistake, rather than a reported flaw in Lighter’s official developer tools, was at the center of the platform’s November 16 security incident. In a report published by November 18, 2026, Lighter said a trader used unofficial signing code that reused a nonce—a value intended to be unique for each signature. That exposed an 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 a Guardian protection mechanism in a smart contract, temporarily pausing withdrawals. According to Lighter, its security committee was then able to return approximately 5 million USDC to the affected trader. Withdrawals had resumed, with backlogged requests still being processed.
For developers handling API access, the report separates a measure already required from planned controls: Lighter now requires a wallet signature for transfers to the public fund pool. It plans to add IP allowlisting, configurable permissions and limits for API keys.