Skip to content
Est. MMXXVIVol. VI · № 389RSS
Blockchain Breaches

An archive of cryptocurrency security incidents — hacks, exploits, bridge failures and rug pulls, documented with on-chain evidence.

Dossier № 386Private Key Compromise

Lighter API Key Exploit

A leaked trading API key let an attacker drain about $10.4 million in USDC from perpetuals DEX Lighter, using a pool-transfer route that skipped the usual withdrawal signature check.

Date
Victim
Lighter
Chain(s)
Status
Partially Recovered

On November 16, 2026, Lighter, a decentralized perpetual-futures exchange that settles on Ethereum using zero-knowledge proofs, lost approximately $10.4 million in USDC after an attacker used a leaked trading API key. Lighter said its protocol and smart contracts were not breached; the loss stemmed from a single trader's compromised key and a withdrawal path that failed to demand the usual wallet signature.

What happened

Lighter lets users delegate trading to API keys so that bots and market makers can place and cancel orders without signing every action by hand. By design, moving funds to a new withdrawal address requires a separate wallet signature, a guardrail that an API key alone cannot satisfy.

The attacker worked around that guardrail. Using a leaked API key tied to one trader's account, they routed funds through a pool-transfer path that did not enforce the same wallet-signature check as a normal new-address withdrawal. At 10:11 UTC the attacker withdrew 10,393,057 USDC from Lighter's contract in a single transaction, then swapped the proceeds through CoW Swap into roughly 5,760 ETH to frustrate any stablecoin freeze.

Lighter paused withdrawals and pool creation within the hour, enabled a contract "Guardian mode" as a precaution, and prepared a contract upgrade through its Security Council. On-chain researchers put the confirmed drain near $10.4 million, though some early estimates ran as high as $15.5 million across two market-maker accounts.

Aftermath

  • Lighter's Security Council recovered about $5 million in USDC and returned it to the affected trader, and withdrawals were restored the same day.
  • The remaining balance — roughly $5 million or more, largely swapped into ETH and held in the attacker's wallet — had not been recovered as of reporting.
  • Lighter said it would require wallet signatures for transfers to public pools, make API-key signatures non-public, and add IP allowlists and configurable permissions for API keys.
  • Lighter did not disclose how the trader's key leaked or whose account it belonged to.

Why it matters

The Lighter incident is a reminder that a venue can be drained without its contracts ever being broken. The ZK-settled core worked as designed; the failure was an access-control gap — a transfer route that trusted an API key where a wallet signature should have been mandatory — combined with a credential that leaked off-chain.

It lands in a brutal run of November 2026 operational compromises, alongside the Mercado Bitcoin exchange drain, where valid signatures from compromised signing infrastructure moved funds the protocol never questioned. The common thread is that key and credential hygiene, not clever math, is the dominant attack surface for exchanges and perps venues: once an attacker holds a usable key and finds a path the signature check does not cover, the chain executes every transfer faithfully. Lighter's fast partial recovery, enabled by a Security Council with upgrade authority, also shows the trade-off such venues accept — the same privileged controls that let a team claw back $5 million are themselves a centralization risk users must weigh.

Sources & on-chain evidence

  1. [01]unchainedcrypto.comhttps://unchainedcrypto.com/lighter-pins-drain-on-traders-leaked-api-key-says-contracts-were-not-hit/
  2. [02]pro.edgex.exchangehttps://pro.edgex.exchange/en-US/news/article/lighter-recovers-5-million-after-10m-api-key-hack
Transactions
  • 0x5b6f27ded0e9a66ef6fa107083e28db9914e46d7635cc5112d760b9cb2f958c9

Related filings