A signing mistake can put funds at risk even when a platform’s official tools are unaffected. In a report published on November 18, 2026, Lighter said a trader used unofficial signing code on the morning of November 16 (UTC). According to Lighter, reusing a signing nonce 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 able to return approximately 5 million USDC to the affected trader. Withdrawals have since resumed, with queued requests still being processed at the time of the report.
For anyone managing API access, the practical distinction is between controls already in place and those still planned. Lighter said it now requires a wallet signature for transfers to the public pool. It plans to add IP allowlists, configurable permissions and limits for API keys; those planned safeguards should not be treated as active yet.

