0x08c74b3308c7…08c74b30

ConfirmedSecurity505 vB171 sat/vB3 min decode

Lighter Restores Withdrawals After API Key Leak, Returns $5 Million in USDC

Lighter reopened withdrawals after its Security Council returned $5 million in USDC to a trader hit by an API key leak; analysts estimate $15.5 million in losses.

Lighter reopens withdrawals after trader’s API key leak, returns about $5 million in USDC
WitnessLighter reopens withdrawals after trader’s API key leak, returns about $5 million in USDCLeamsii / pixabay

Outputs

  1. Lighter returned about $5 million in USDC to the affected trader via its Security Council.

  2. On-chain analysts Lookonchain and Onchain Lens estimated total losses at $15.5 million.

  3. Withdrawals reopened Monday after Guardian Mode was deactivated.

  4. The breach stemmed from nonce reuse in non-official signing software that exposed the private key.

  5. Transfers into public pools now require a wallet signature; API key signatures are non-public.

Lighter, the Ethereum-based perpetual futures exchange, reopened deposits and withdrawals on Monday after its Security Council deactivated Guardian Mode and returned approximately $5 million in USDC to a trader whose API keys were compromised.

The exchange disclosed the recovery in a postmortem published after the incident. Lighter initially reported a suspected compromise involving one external party and suspended withdrawals and pool creation as a precaution. The team later identified a leaked API key tied to a specific trader's account and made recovering funds from an additional withdrawal attempt its priority.

"Deposits and withdrawals are back to normal following the deactivation of Guardian Mode by the Lighter Security Council," Lighter announced.

How much was actually stolen?

Lighter did not disclose the total size of the theft or the identity of the affected trader. On-chain analysts Lookonchain and Onchain Lens estimated losses at $15.5 million and suggested the compromised account belonged to Abraxas Capital, a trading firm. The roughly $5 million in USDC returned by the Security Council represents only part of that estimated figure.

According to the postmortem, the exchange's smart contract Guardian detected the anomaly and temporarily paused withdrawals, which gave the Security Council the window needed to return the funds to the trader.

How did the attacker drain the account?

The attacker used the compromised account to open a public pool, then minted shares in a separate account they controlled, Lighter said. They transferred the trader's funds into the pool without minting additional shares, inflating the value of the attacker's existing shares. The attacker redeemed those shares and withdrew the proceeds.

The root cause, per Lighter's report, was nonce reuse. The API keys leaked through the account's own signatures, generated by signing software from outside Lighter's official software development kits. The signatures reused nonces — the one-time values required for each signature. When two public signatures use the same nonce and key, anyone can derive the private key from them, the report explained.

Lighter stated that its official SDKs, protocol, smart contracts and infrastructure were not affected.

What has changed operationally?

The exchange has restructured how API keys interact with its pools:

  • An API key alone can no longer authorize a transfer to a public pool.
  • Transfers into public pools now require a wallet signature.
  • API key signatures have been made non-public.
  • The team is adding IP allowlists and per-key permissions, including restrictions on which markets an individual key can trade.

The changes shift the exchange from a single-credential model toward layered authorization, reducing the blast radius of any single leaked key. For a derivatives venue where API-driven trading dominates, the wallet-signature requirement adds friction to automated strategies but closes the exact vector used in this incident.

Lighter has not said whether it will pursue recovery of the remaining estimated losses or whether law enforcement is involved. The Security Council's Guardian mechanism, which fired automatically on Monday, remains the exchange's last line of defense for future anomalies.

via x.com (Original)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,374 articles