CyberSIXT reportingUpdated
Lighter DEX exploit drains $10.4M via a trader's leaked API keys
Part of the Lighter story · since 16 Nov
- Mon 16 Nov, 11:39 UTC. cybersixt, first report. Lighter DEX exploit drains $10.4M via a trader's leaked API keys. This article, 1st of 1.
Updated 16 November, 18:38 UTC. Lighter says the trader's keys leaked through nonce reuse in non-official signing code; about $5 million was returned and withdrawals resumed.
The trader's API keys that were used to drain funds from Lighter on 16 November leaked through the trader's own signatures: the account's signing code reused nonces, which let anyone calculate the private keys from public data, Lighter says in a post-incident write-up published at 18:20 UTC. The affected accounts were not using Lighter's official SDKs, and Lighter says its protocol, smart contracts and infrastructure were not affected. About $5 million in USDC has been returned to the trader, and deposits and withdrawals are back to normal.
How the keys leaked
Every transaction on Lighter, a perpetual futures exchange that runs on its own zero-knowledge rollup on Ethereum, is authorised by a signature from an API key, and each signature uses a one-off random value called a nonce. Lighter's signatures were public. If the same key signs two different transactions with the same nonce, the private key can be worked out from the two signatures, a well-known weakness that applies to Bitcoin and Ethereum signatures too. The affected accounts' signing code had been reusing nonces, so the attacker needed no access to the accounts or to Lighter's systems.
An API key cannot withdraw to someone else's wallet, but it can move funds to its own account's sub-accounts, and a public pool the account creates counts as one. With the leaked key the attacker created a public pool from the victim's account, minted pool shares from an account the attacker controlled, moved the victim's funds into the pool without minting new shares, which raised the value of the attacker's shares, then redeemed them and withdrew. That matches the analyst accounts we reported earlier.
What was recovered
Lighter says its smart contract Guardian, a safety mode it had enabled earlier, was triggered by the anomaly and paused withdrawals, which let the Lighter Security Council return about $5 million in USDC to the affected trader, the funds tied to the attacker's second withdrawal attempt. The first withdrawal had already gone: at 10:11 UTC a transaction moved 10,393,056 USDC out of the Lighter contract on Ethereum to 0xb3fffca23d4444ee73349825acd84f7b5020e387, which swapped it for ETH and began moving it on. Blockchain security firm PeckShield says part of it was bridged to Hyperliquid and turned into Monero, which is far harder to trace. Lighter has not given a final loss figure.
What Lighter is changing
Lighter now requires a wallet signature on top of the API key to move funds into a public pool, and has made API key signatures non-public. It is adding IP allowlists for API keys, per-key permissions and limits on actions and markets, and monitoring of signatures for nonce reuse, and says it will contact affected accounts and void their keys.
What traders should do
Anyone trading on Lighter programmatically should sign with an official Lighter SDK (Python, Go, TypeScript or the Agent Kit), which generate every nonce with a cryptographically secure random number generator. Custom or third-party signing code must never derive a nonce from a timestamp, a counter, a weakly seeded random generator, the transaction contents or a cached value. If there is any chance a key has signed with a repeated nonce, rotate every API key. The same check applies to any trading bot or wallet code that implements ECDSA or similar signatures itself.
What is not known
Lighter has not named the trader or said which signing code reused nonces, how much in total was lost, or whether other accounts were exposed the same way. It first suspended withdrawals at 11:02 UTC.
How the story developed
1 article from 1 outlet since 16 Nov. Still developing; the latest report was 11 hours ago. This was the first report.
- Mon 16 Nov, 11:39 UTC. cybersixt, first report. Lighter DEX exploit drains $10.4M via a trader's leaked API keys. This article, 1st of 1.
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 1 articles as a listHide the list
- Mon 16 NovDay 01
- Lighter DEX exploit drains $10.4M via a trader's leaked API keys11:39 · cybersixt · First report · This article, 1st of 1
Sources
- Lighter on X: Signing Safely on Lighter, lessons from November 16Primary sourcex.com
- Lighter on X: deposits and withdrawals back to normalPrimary sourcex.com
- Lighter on X: leaked API key, Guardian modePrimary sourcex.com
- Lighter on X: security incident, withdrawals suspendedPrimary sourcex.com
- Blockscout: 10.39M USDC withdrawal from the Lighter contractPrimary sourceeth.blockscout.com
- Blockscout: Lighter USDC contract on EthereumPrimary sourceeth.blockscout.com
- Blockscout: attacker addressPrimary sourceeth.blockscout.com
- PeckShield on X: ETH bridged to Hyperliquid to buy XMRx.com
More reporting
- Suspected Optimizely breach planted card stealer on 186 websites16 Nov
- BundID cyberattack locks German accounts, email codes now required16 Nov
- Trezor data breach at shipping partner exposes 27,000 orders16 Nov
- Fugaku supercomputer hit by cyberattack, users' SSH keys stolen16 Nov
- Coles cyber incident: no evidence of customer data breach so far16 Nov
Written by CyberSIXT from the sources above.How we reportCorrectionsRSS