Lighter exchange loses $10.4 million USDC in API key breach, restores withdrawals
A nonce‑reuse flaw in custom API signing code let attackers move over $10 million USDC from Lighter, prompting new key controls and a partial fund return.
Key takeaways
- Bitquery traced a 10,393,057 USDC outflow from Lighter on November 16, 2026.
- Lighter returned roughly $5 million USDC to affected traders while the rest remains unrecovered.
- The exchange now requires wallet signatures for pool transfers and is adding IP allowlists and scoped API permissions.
The decentralized perpetual futures platform Lighter confirmed that a security incident on November 16, 2026 resulted in the unauthorized transfer of about $10.4 million USDC. The loss was traced to compromised API signing keys that suffered a nonce‑reuse vulnerability in custom client code, not to a flaw in the platform’s smart contracts. Lighter has resumed deposits and withdrawals, returned roughly $5 million to affected traders, and announced a suite of new controls for API access.
Root cause: nonce reuse in unofficial signing code
According to the post‑mortem released by Lighter and reported by NewsBTC, several trader accounts used non‑standard signing libraries that reused one‑time cryptographic values (nonces). Reusing a nonce with an incorrect signature scheme can enable an attacker to reconstruct the private key, allowing them to issue signed instructions as if they were the legitimate account holder. The breach therefore stemmed from a client‑side cryptographic error rather than a vulnerability in the exchange’s core protocol.
Scale of the outflow and partial recovery
Blockchain analytics firm Bitquery identified a single withdrawal of 10,393,057 USDC from a Lighter‑related Ethereum contract on the day of the incident. The funds were quickly converted to ether and moved through multiple wallets, creating a visible trail but not yet a fully reconciled loss figure. Lighter reported that about $5 million USDC has been returned to the impacted trader, while the remainder of the outflow is still under investigation.
New security measures and future safeguards
In response, Lighter has activated several mitigations: wallet signatures are now mandatory for any transfer into public liquidity pools, and API‑key signatures are no longer exposed publicly. The platform also plans to implement IP allowlists, per‑key permission scopes, configurable limits, and monitoring for repeated nonces. These steps aim to close the gap between credential permissions and the financial impact they can generate, a point emphasized by Cointelegraph’s analysis of the incident.
What to watch next
Observers will be looking for a detailed reconciliation report that quantifies the final loss, the amount of recovered funds, and the effectiveness of Lighter’s new controls under live trading conditions. Additional scrutiny may focus on whether other decentralized derivatives venues are using similar custom signing implementations and how quickly they adopt vetted cryptographic libraries.
Frequently asked questions
What is nonce reuse and why is it dangerous?
Nonce reuse occurs when a cryptographic signature uses the same one‑time value more than once, allowing an attacker to derive the private key and forge valid signatures.
Did the attack exploit Lighter’s smart contracts?
No, the breach was caused by compromised API keys due to faulty client‑side signing code; the platform’s smart contracts remained intact.
Sources
Get stories like this in your inbox
The day’s biggest crypto stories and market moves in one short morning email. Free, no spam.