0x2df904f02df9…2df904f3

ConfirmedSecurity797 vB52 sat/vB4 min decode

Lighter Froze Withdrawals and Returned $5M After API Key Leak

Lighter's Guardian contract paused withdrawals on November 16 after an attacker used leaked API keys and a public pool to extract roughly $5 million in USDC from one trader's account.

Lighter Froze Withdrawals and Returned $5M After Third-Party Code Leaked an API Key
WitnessLighter Froze Withdrawals and Returned $5M After Third-Party Code Leaked an API KeyAI-generated

Outputs

  1. Lighter's Security Council returned roughly $5 million in USDC to one affected trader on November 16.

  2. The attack exploited a nonce-reuse flaw in third-party signing code, not Lighter's own SDKs.

  3. Guardian Mode paused withdrawals; deposits and withdrawals resumed at 18:31 UTC the same day.

  4. $LIT traded at $2.87 on November 18, down 4.4% in 24 hours, per CoinGecko.

  5. Lighter plans IP allowlists and configurable per-key limits for future API key protections.

Lighter returned approximately $5 million in USDC to a single affected trader on November 16, after an attacker seized control of that trader's API keys and drained the account through a public pool — and the venue's smart-contract Guardian froze every user's withdrawals to make it possible. Deposits and withdrawals resumed at 18:31 UTC the same day, according to a post on Lighter's announcements channel: "Deposits and withdrawals are back to normal following the deactivation of Guardian Mode by the Lighter Security Council."

The incident, explained in a company post titled "Signing Safely on Lighter: Lessons from November 16," turned a trading-only credential into a full cash exit. The keys leaked through the account's own signatures. The venue attributes the cryptographic failure to third-party signing software, not its infrastructure: "The official Lighter SDKs generate nonces safely and were not affected."

How a trading key became a withdrawal route

Lighter's API key documentation draws a strict boundary. A key can trade, cancel, modify orders, adjust leverage, manage sub-accounts and authorize secure withdrawals. It cannot, on its own, transfer funds to another L1 owner, execute a fast withdrawal, or approve a fee-charging integrator — those require the owning wallet's signature. "Secure withdrawals only need the API key because they can only go back to the L1 address that created the account," the documentation reads.

So the attacker could not simply send the balance elsewhere. Instead, per Lighter's four-step account of the sequence, they created a public pool from the affected account, minted pool shares in a separate account they controlled, moved the affected account's funds into the pool in a way that raised net asset value without minting matching shares, then redeemed and withdrew. Every step was a legitimate operation. Together they routed value out through an authorized path.

Public pools carry no lockup period, per Lighter's documentation, while a separate protocol liquidity pool has a five-minute withdrawal cooldown. Lighter also notes that a live key carries broader risk regardless: a holder can trade against the owner at bad prices in thin markets or open heavily leveraged positions that expose the account to liquidation.

Where the failure actually sat

The root cause is nonce reuse. Every Lighter transaction requires a signature with a unique, unpredictable nonce. Signatures are public. If the same nonce signs two different transactions with the same key, the private key can be computed from the pair. "This issue isn't specific to Lighter," the post notes — it applies to Bitcoin and Ethereum signatures as well.

That places the defect in signing software the affected accounts chose to run. The exposure sits with traders who wrote their own signers, adapted unofficial libraries, or run automated agents against the exchange API. Lighter's instruction to them is blunt: "If you're unsure whether your code has ever reused a nonce, rotate all of your API keys and switch to an official SDK."

What does the Guardian pause change?

"Our smart contract Guardian was triggered by the anomaly, which temporarily paused withdrawals and allowed ~5MM $USDC to be returned to the affected trader by the Lighter Security Council," the post states. A venue-wide halt, decided by a council, executed through a privileged contract path and disclosed afterwards on social media, is a recognizable pattern in crypto and an unfamiliar one in regulated venue practice, where halts carry written triggers, named decision-makers, maximum durations and reporting duties.

Three things are missing from the record: Lighter did not publish when Guardian triggered, so the freeze duration is unknown. It did not state the total value taken, only the amount returned. And it did not say whether the returned USDC came from recovered attacker funds or the Security Council's own resources — the difference between a recovery and a discretionary bailout of one account.

Market context and what comes next

Per CoinGecko, $LIT traded at $2.87 at 03:58 UTC on November 18, down 4.4% over 24 hours, with a market capitalization near $718 million and $81.1 million in daily volume. The $5 million return equals roughly 0.70% of market capitalization. Lighter fell 12.7% between the November 14 and 16 closes, but most of that move preceded the disclosure, and bitcoin fell 4.4% over the same window — no causal link is established.

Lighter says it is "adding further protections, including IP allowlists and configurable limits per API key." Those reduce blast radius after a leak. Whether the venue also ships the design change its own post implies — making API key signatures non-public, removing the attack class entirely — and whether it publishes a loss figure and a halt standard, will define whether this incident was fully contained.

via cryptonews.net (Source)

More from Marcus Bennett

Marcus Bennett

Show full bio

Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,456 articles