Withdrawals resume after an emergency pause

Decentralized perpetual futures platform Lighter has restored deposits and withdrawals after a compromised trader account triggered an emergency pause on November 16. In its postmortem, Lighter said its smart-contract Guardian detected anomalous activity and temporarily stopped withdrawals. The platform’s Security Council later disabled Guardian Mode after returning approximately 5 million USDC to the affected trader, and pending withdrawal requests began processing. Lighter described the incident as an account-key failure rather than a compromise of its protocol, contracts or infrastructure.

Reused signing nonces exposed private keys

Lighter said the affected accounts used signing software outside its official software development kits. That code reused cryptographic nonces, one-time secret values that must be unique for each signature. When the same key signs two different messages with the same nonce, an observer can use the public signatures to calculate the private key. According to Lighter, the attacker needed no access to the trader’s systems or to Lighter itself because the vulnerable signatures were publicly visible. The platform said its official SDKs generated nonces securely and were not affected.

Related reporting: Study Finds AI Agents Raised Their Own Crypto Spending Caps

A public pool provided the route out

An API key could not send funds directly to another person’s wallet, so the attacker used Lighter’s public-pool mechanics. The postmortem says the attacker created a pool from the compromised account, minted pool shares from a separate account under the attacker’s control, and then transferred the trader’s funds into the pool without issuing additional shares. That increased the value of the attacker’s existing pool position, which could then be redeemed and withdrawn. The sequence used authorized account functions after the key had been recovered from the repeated signatures.

The confirmed recovery is narrower than loss estimates

Lighter confirmed that its Security Council returned about 5 million USDC, but it did not publish a final total for funds taken. Independent reporting cited onchain estimates ranging above that amount, including a roughly $10.4 million observed USDC withdrawal, but those figures should not be treated as Lighter-confirmed losses. The Block and Unchained separately reported the restoration of withdrawals and the approximately 5 million USDC return. The identity of the affected trader also remains undisclosed by Lighter.

Two protections are already live

Lighter says transfers into public pools now require a wallet signature, preventing an API key alone from using the same route. It has also made API-key signatures non-public. The platform plans IP allowlists, configurable permissions and limits for individual keys, and monitoring that can identify nonce reuse and invalidate affected credentials. Those planned controls do not yet have implementation dates. Lighter advised users of custom or third-party signing code to rotate their API keys if they cannot rule out nonce reuse and to switch to an official SDK.

The postmortem shifts attention to integration security

The incident shows how external trading software can create a loss path even when an exchange’s core contracts remain intact. Programmatic traders depend on key-generation, signing and nonce-handling code that may sit outside the venue’s direct control. Lighter’s new wallet-signature requirement narrows one route for moving value, while private signatures reduce the information available to an observer. The remaining questions are whether all affected accounts have rotated vulnerable keys, when the planned restrictions will arrive and whether future monitoring can detect nonce reuse before an attacker acts.

Sources

AI-generated editorial image; not a photograph of the reported event. Prepared with AI assistance and source verification.