Lighter Reopens Withdrawals After Trader’s API Key Leak, Returns $5 Million in USDC

Lighter reopened deposits and withdrawals after its Security Council returned about $5 million in USDC to a trader whose API key was leaked through a nonce-reuse bug in third-party signing software.

Get a summary in:
Blockchain network illustration representing a DeFi exchange
Follow Teck Hustlers on Google
Add Teck Hustlers as a preferred source to see more of our stories in Google Top Stories.
Add as preferred source on Google

TL;DR: Lighter, an Ethereum-based perpetual futures exchange, reopened deposits and withdrawals on November 17 after its Security Council returned roughly $5 million in USDC to a trader whose account had been drained through a leaked API key. The breach traced back to reused cryptographic nonces in signing software from outside Lighter’s official developer kit, not a flaw in the exchange’s own smart contracts. Lighter has since barred API keys from authorizing pool transfers on their own and added IP allowlists for individual keys.

Golden padlock sitting on a computer keyboard, representing API key security

The incident started Monday when Lighter flagged a suspected compromise tied to a single external account and paused withdrawals and public pool creation as a precaution. Within hours the exchange traced the problem to a leaked API key belonging to one trader, and said recovering the stolen funds was its top priority before it would reopen the platform.

Lighter’s own smart contract Guardian had already done some of the work. The anomaly tripped a temporary pause on withdrawals, buying the exchange’s Security Council enough time to claw back the money before it left the protocol entirely. By the end of Monday, Lighter said contract upgrades were complete and normal service had resumed.

How the attacker pulled it off

The mechanics described in Lighter’s postmortem are a textbook case of a signature scheme going wrong outside the core protocol. The trader’s API keys were compromised because the signing software they used, built outside Lighter’s official SDKs, reused nonces across transactions. A nonce is a one-time value that should never repeat; when two signatures share the same nonce and key, an attacker can work out the private key just by comparing them.

Once the attacker had that key, they opened a public pool using the compromised account, then minted pool shares from a separate wallet they controlled. They moved the trader’s funds into the pool without minting any new shares themselves, which inflated the value of the shares they already held. Redeeming those shares let them pull the trader’s money out before Lighter’s Guardian froze things.

Lighter did not disclose the full size of the theft or name the affected trader. Onchain analysts Lookonchain and Onchain Lens pegged the total loss closer to $15.5 million and pointed to Abraxas Capital as the likely victim, a larger figure than the roughly $5 million Lighter confirmed it had returned. The gap suggests either a partial recovery or a difference between gross outflows and what the Security Council was able to claw back before funds left the pool.

This kind of nonce collision is not new to crypto security researchers. We covered a related weakness when Solana moved to retire durable nonces across its ecosystem (here), part of a broader industry push to close off the exact class of signature replay and reuse bugs that hit Lighter’s trader. Wallet and signer compromises tied to key handling outside official tooling have also shown up before, including the breach that hit Web3Auth and Keplr users (covered here), where custody of the signing process, not the underlying chain, was the weak point.

What Lighter changed afterward

Lighter’s response focused squarely on the attack surface that failed: API key permissions. An API key can no longer authorize a transfer into a public pool by itself. Any transfer now requires a wallet signature on top of the key, and API key signatures have been made non-public so they cannot be harvested and compared the way the attacker’s were. The exchange is also rolling out IP allowlists and per-key permissions, including restrictions on which markets an individual key is allowed to trade.

“Deposits and withdrawals are back to normal following the deactivation of Guardian Mode by the Lighter Security Council,” the exchange said in its announcement reopening the platform. Lighter was explicit that its official SDKs, protocol, smart contracts, and core infrastructure were never touched. The failure sat entirely in how a trader generated signatures using tools outside the sanctioned stack, a distinction that matters for anyone assessing counterparty risk on the exchange going forward.

The token LIT jumped nearly 15% following the disclosure and resolution, a reaction more consistent with relief that the exchange contained the damage quickly than with a market pricing in a protocol-level failure.

Why this matters beyond one exchange

Perpetual futures DEXs have become one of the more competitive corners of crypto infrastructure this year, and Lighter has built real market share in that race. A security incident at any major venue tends to get read as a referendum on the whole category, which is part of why the exchange moved so fast to publish a detailed postmortem rather than let onchain sleuths define the story.

The bigger lesson is about where trust actually breaks in DeFi. Lighter’s smart contracts held up exactly as designed. The Guardian mechanism did its job. What failed was a third-party signing tool a trader chose to use instead of the exchange’s own SDK, and a nonce reuse bug inside it that has sunk other systems before. For traders running their own automation or using API keys with any exchange, the incident is a reminder that key hygiene and signing software provenance matter as much as the security of the protocol itself. An API key is only as safe as the code that generates its signatures, and outsourcing that code to an unofficial tool quietly moves the trust boundary somewhere nobody is auditing.

The bottom line

Lighter handled this about as well as a hot-key compromise can be handled: it caught the anomaly, froze withdrawals before the bulk of the funds left the protocol, and returned roughly $5 million to the affected trader within a day. But the root cause, a trader using third-party signing software with a nonce reuse bug, is a problem that will keep recurring across DeFi until more exchanges simply refuse to accept signatures generated outside their own vetted tooling. Until then, every API key is a liability that extends well past the exchange’s own code.

Follow Teck Hustlers on Google
Add Teck Hustlers as a preferred source to see more of our stories in Google Top Stories.
Add as preferred source on Google
About

The Teck Hustlers Editorial Team covers technology, business, finance and gaming news for readers who want the story behind the headline. Every article is researched, written and edited by our in-house team, checked against company announcements, filings and reputable reporting, and updated when new facts emerge. We focus on what each development means for founders, professionals, investors and everyday users. Have a tip or a correction? Reach us through our contact page.

Up next: Single-Member LLC: How It Works, Taxes and Pros and Cons