Lighter returns 5m USDC after API key exploit and restores withdrawals
Trading platform Lighter retrieved approximately 5 million USDC after an attacker exploited unofficial signing code. Core smart contracts were unaffected and withdrawals have resumed.

Key takeaways
- 1Lighter returned 5 million USDC to an affected trader following a security breach.
- 2The attacker derived private API keys by exploiting nonce reuse in unofficial signing code.
- 3Core smart contracts, protocol infrastructure, and official SDKs were unaffected.
- 4Lighter activated its Guardian mechanism to pause withdrawals until the Security Council recovered the funds.
- 5New security measures include mandatory wallet signatures for public pool transfers and non-public API signatures.
Trading platform Lighter has returned approximately 5 million USDC to an affected trader following a security incident caused by cryptographic nonce reuse in unofficial signing code, the project announced in a security report on 16 November 2026. The platform's security mechanisms temporarily halted system withdrawals during the incident, but normal operations have now resumed and pending payout requests are actively being processed.
The exploit targeted specific trading accounts that used unofficial signing code to generate signatures. Because this third-party code reused cryptographic nonces when creating signatures, an attacker was able to perform mathematical calculations on public signatures to derive the private API keys associated with those accounts. Once the attacker obtained the private key, they accessed a compromised account to create a public liquidity pool, transferred funds into that pool, and extracted the assets by redeeming pool shares through a separate account under their control.
Lighter confirmed that its core protocol architecture, smart contracts, primary infrastructure, and official software development kits remained completely unaffected throughout the event. The underlying smart contract layer functioned as designed, and the breach was entirely confined to off-chain key derivation issues resulting from the use of third-party client code.
The unusual account activity activated Lighter's smart contract-based Guardian mechanism, an automated emergency tool designed to protect platform assets. The Guardian mechanism triggered a temporary pause on all withdrawals across the network, giving the platform's Security Council time to isolate the compromised accounts, secure the system, and recover the stolen assets. The Security Council successfully retrieved the 5 million USDC and transferred the full amount back to the affected trader before reopening withdrawals.
In response to the incident, Lighter introduced immediate structural updates to protect users from signature extraction vulnerabilities. The platform now requires explicit wallet signatures for all transfers involving public pools, adding a secondary layer of authentication beyond API keys. Additionally, Lighter altered how cryptographic signatures are handled, making API key signatures non-public so external observers cannot inspect them to attempt key derivation.
Lighter is also developing additional security controls to prevent future key compromises. The platform plans to implement IP allowlists that restrict API key execution to approved network addresses, along with granular per-key permissions and strict transaction limits. To address ongoing risks from custom user software, Lighter will deploy automated monitoring systems designed to detect nonce reuse patterns in real time and automatically revoke any exposed API keys.
Cryptographic nonce reuse is a well-known vulnerability in digital signature schemes like ECDSA. When the same random value or nonce is used to generate multiple signatures under the same private key, an attacker can extract the private key using standard algebraic methods. Official software development kits incorporate safeguards to ensure nonces are unique for every transaction, but custom or third-party implementations frequently omit these safeguards or rely on weak random number generators.
Automated safety controls like Lighter's Guardian mechanism demonstrate how decentralized trading protocols manage security risks originating outside their core smart contracts. By pausing withdrawals when abnormal activity occurs, protocol safety tools give governance teams and security councils the opportunity to resolve external key breaches without requiring contract upgrades or rollbacks to the underlying blockchain.
Traders using custom API scripts or third-party integration tools on decentralized platforms remain responsible for checking their signing libraries. Lighter advised automated traders to verify that their software uses unique nonces for every signed payload and to migrate away from unverified third-party code bases.
Reported and edited by the YourKhabri desk under our editorial policy. Nothing here is investment advice.


