Lighter trader API keys (November 2026) hack — November 2026
Incident facts
| Date of incident | |
|---|---|
| Publicly disclosed | November 16, 2026 |
| Target type | Decentralised exchange |
| Loss | $10,393,057Price at time of incident |
| Method | Private key compromiseThe affected accounts signed with third-party code, not Lighter's official SDKs, that reused signing nonces, so their API private keys could be computed from public signatures; with the keys the attacker created a public pool from the victim account, transferred its funds into the pool and redeemed shares held by an attacker account |
| Chains | Ethereum |
| Outcome | Unresolved |
What happened
On the morning of 16 November 2026 (UTC) an attacker took control of the API keys of a trader's accounts on Lighter, a perpetual futures exchange that runs as a zero-knowledge rollup settling on Ethereum, and moved the funds out. According to Lighter's post-mortem, the affected accounts signed their requests with unsafe code other than Lighter's official SDKs, and that code reused signing nonces, so the private keys could be calculated from public signatures. The attacker used a key to create a public pool from the victim's account, minted pool shares in a separate account, transferred the victim's funds into the pool and redeemed the shares. Lighter says its protocol, smart contracts, infrastructure and official SDKs were not affected.
One wallet withdrew 10.39 million USDC to Ethereum (the figure here) and swapped it to ETH on CoW Swap within four minutes; Bitquery followed 1,920 ETH through twelve new wallets to Hyperliquid, where each bought XMR1, a Monero-named token. Lighter paused withdrawals and pool creation at about 11:00 UTC. Its Guardian contract mechanism caught a further withdrawal attempt, and the Lighter Security Council returned about 5 million USDC to the affected trader; that money had not left Lighter, so it is excluded here rather than counted as recovered. Posts on X put the total across two market-maker accounts at about $15.5 million, a figure Lighter has not confirmed.
Withdrawals reopened the same day. Lighter now requires a wallet signature for transfers into public pools, has made API key signatures non-public, and plans IP allowlists and per-key limits. It has not said whether the trader will be compensated for the withdrawn funds.
On-chain references
Published so the figures above can be checked against the chain rather than taken from us. Victim addresses are never listed.
Attacker addresses
- 0xb3fffca23d4444eE73349825ACD84f7b5020e387
Sources
- Lighter post-mortem: Signing Safely on Lighter (16 November 2026)Primary · retrieved 2026-11-18
- Lighter on X (16 November 2026, 12:49 UTC)Primary · retrieved 2026-11-18
- Bitquery investigation (16 November 2026)Secondary · retrieved 2026-11-18
- Crypto Briefing (16 November 2026)Secondary · retrieved 2026-11-18
- SlowMist Hacked database, Lighter entry (16 November 2026)Aggregator · retrieved 2026-11-18
Official post-mortem: https://x.com/Lighter_xyz/article/2122394446343946717
Changes to this entry
- Added at the 10.39m USDC withdrawn to Ethereum (Bitquery; SlowMist $10,393,057). The ~5m USDC the Security Council returned to the trader came from a further withdrawal attempt that never left Lighter, so it is excluded (Arcus precedent), not counted as recovered. The $15.5m two-account total on X is unconfirmed by Lighter.
Cite this
This data is published under CC BY 4.0. You may reuse it, including commercially, as long as you credit iTokenly and link back.
iTokenly Hack Registry, "Lighter trader API keys (November 2026) hack — November 2026", iTokenly, accessed 2026-11-18, https://itokenly.com/hacks/lighter-trader-api-keys-november-2026https://itokenly.com/hacks/lighter-trader-api-keys-november-2026Permalinks never change. If an entry is renamed, the old address keeps working.
Spotted an error? Write to [email protected]. Corrections to published figures are logged on this page. See the methodology for how entries are checked.