0x7a44a1ee7a44…7a44a1f1

ConfirmedSecurity508 vB60 sat/vB3 min decode

Lighter Recovers About 5 Million USDC After API Key Leak

Lighter helped traders recover about 5 million USDC after nonce reuse in unofficial signing code let attackers reconstruct API keys from public signature data. Withdrawals have resumed.

Lighter Helps Traders Recover About 5 Million USDC After API Key Leak
WitnessLighter Helps Traders Recover About 5 Million USDC After API Key LeakPexels / pixabay

Outputs

  1. Lighter helped affected traders recover approximately 5 million USDC after an API key leak.

  2. The leak stemmed from reused nonces in unofficial signing code; attackers reconstructed keys from public signature data.

  3. Lighter's official SDK, protocol, smart contracts and infrastructure were unaffected.

  4. Guardian mode has closed and withdrawals have resumed, with pending requests being processed.

  5. Planned controls include IP allowlists, permission controls and per-key market limits.

Perpetuals exchange Lighter has helped affected traders recover approximately 5 million USDC following an API key leak traced to nonce reuse in unofficial signing code. The company has closed Guardian mode, restored withdrawals, and is now processing all pending withdrawal requests.

The recovery figure is an approximation, and Lighter has not stated what share of total losses the 5 million USDC represents. The leak did not originate in Lighter's own tooling: the company traced it to repeated nonce values in signing code used by affected accounts. Attackers exploited public signature data to reconstruct the API keys of those accounts.

What remained intact?

Lighter's official software development kit was unaffected by the incident. The protocol itself, its smart contracts, and its infrastructure also remained unaffected, according to the company's account. That distinction matters: the failure occurred in code that users adopted outside Lighter's supported stack, not in the exchange's core systems.

The claim that all on-chain components were untouched rests on Lighter's own disclosure; no independent audit findings have been published alongside it. Users evaluating the incident should note what the statement does not address — specifically, how many accounts were affected and over what period the reconstruction of keys occurred.

Which security changes has Lighter made?

Lighter has already implemented two changes. It now requires a wallet signature for transfers to a public fund pool, and it has made API key signatures private rather than publicly readable.

Additional measures are planned but not yet live:

  • IP allowlists for API access
  • Permission controls on keys
  • Limits on which markets an individual API key can trade

The company's listed security measures also include monitoring for nonce reuse, contacting affected accounts, and revoking keys tied to the incident. Planned controls carry no stated rollout dates, so traders cannot yet verify when the permission and market-access limits will take effect.

Why did nonce reuse expose the keys?

Reusing a nonce in signature schemes is a well-documented cryptographic failure: when the same nonce signs two different messages, the mathematics of the scheme can reveal the underlying private key. In this case, attackers did not need to break the scheme itself. They only needed public signature data from accounts whose unofficial signing code repeated nonce values, which allowed them to reconstruct the API keys deterministically.

The vector is instructive for the broader trading ecosystem. Any user who ran third-party or self-written signing code against Lighter's API carried risk that the official SDK did not carry, and no exchange-side control existed to catch the repetition before keys leaked.

What happens next?

Withdrawals have resumed, and Lighter says it is working through the pending request queue. The operational burden now shifts to verification: affected traders must confirm their recovered balances, and the market will watch whether the promised IP allowlists, permission controls, and per-key market limits ship in a reasonable window. Until those controls are live, the same class of exposure — unofficial tooling repeating nonces against a public API — remains structurally possible.

via tokenpost.com (Source)

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.

1,525 articles