CoinSleuth

Lighter says reused signing nonce exposed trader’s API key; withdrawals resumed

A trader’s choice of signing code can affect the security of funds even when a platform’s official tools are unaffected. In a security review reported on November 18, 2026, Lighter said a trader using unofficial signing code reused a signing nonce on the morning of November 16 (UTC). According to Lighter, 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 not affected. It said the unusual activity triggered a smart-contract Guardian safeguard, temporarily pausing withdrawals. Lighter’s security committee was then able to return approximately 5 million USDC to the affected trader. Withdrawals have resumed, and the platform said it was processing a backlog of requests.

Lighter said it 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; those measures were not described as already in place. For readers managing API access, the incident illustrates why the signing code used with a key matters as much as where the key is stored.

Further reading