About $10.4 million in USDC left Lighter, a crypto futures exchange, on Monday after an attacker got hold of one trader's API keys. Lighter says the trader's own signing software reused a one-time number, so the keys could be calculated from public data. The exchange says its contracts were not hacked and that it returned about $5 million to the trader.

Key facts

  • Who: Lighter, a decentralized futures exchange that settles on Ethereum, and one trader's account
  • What: An attacker used the trader's API keys to move funds into a pool and withdraw them
  • When: Monday, November 16, 2026, at 10:11 am UTC
  • How much: About $10.4 million in USDC withdrawn; about $5 million returned to the trader
  • Source: Cointelegraph report with Lighter's postmortem

The Lighter exploit was not a break-in to the exchange itself, Lighter says. It was one trader's keys. On Monday an attacker withdrew about $10.4 million in USDC from Lighter, a crypto futures exchange, using that trader's API keys, the codes that let software trade on an account.

Many active traders run bots that sign orders with one. Lighter's postmortem says the problem began in software the trader built for that job, Cointelegraph reported.

How the keys leaked

Each signed order uses a random number, called a nonce, that should never be repeated. The trader's homemade tool reused them. When that happens, anyone who collects the public signatures can do the math and recover the private key, the secret that makes the signatures.

With the keys, the attacker created a public pool, moved the trader's funds into it, and withdrew them to an account they controlled. The wallet pulled $10.39 million at 10:11 UTC, nearly an hour before Lighter's first public post, Unchained found on Ethereum records.

What Lighter did next

Lighter switched on what it calls Guardian mode, which paused withdrawals and new pools. Its Security Council returned about $5 million in USDC to the trader, and withdrawals reopened the same day. Lighter says its contracts and its official developer kits were not affected.

It has also made API-key signatures private and now requires a wallet signature to send funds to a public pool. It says it plans to add IP allowlists and limits on what each key can do.

What's still unclear

One researcher put losses at $15.5 million across two market-maker accounts. Lighter cites one account and has not confirmed that figure. Blockchain firm Bitquery traced part of the money into ETH and then to Hyperliquid, but warned that similar routes alone don't prove the same thief hit other platforms.

If you trade with API keys

  • Use the exchange's official tools or developer kit to sign orders. Homemade signing code is where this went wrong.
  • Give each key only the rights it needs. A trading bot rarely needs to withdraw or transfer.
  • Turn on IP allowlists wherever an exchange offers them, so a stolen key fails from other computers.
  • Keep bot funds in a separate account with only what the bot uses, and delete keys you no longer run.

This attack needed a leaked key, so traders who never made one were not exposed to this flaw. Our report on API keys drained after the Railway breach shows the same lesson from another angle.

Sources: Cointelegraph, Lighter recovers $5M after $10M exploit linked to compromised API keys (November 16, 2026, updated 20:40 UTC), Unchained, Lighter Pins Drain on Trader's Leaked API Key as Sleuths Say $15M Lost (November 16, 2026).