Loading prices…
🔥BULLISH

Lighter Returns $5M USDC, Resumes Withdrawals

The loss came from account-level API key exposure, not the protocol itself, and Lighter says its core systems remain unaffected.

Lighter's November 16 security incident report said an attacker exploited nonce reuse in unofficial signing code used by certain trading accounts, allowing API private keys to be derived from public signatures. The attacker then created a public pool through a compromised account, transferred funds into it and extracted assets by redeeming pool shares through an attacker-controlled account.

Why it matters

Lighter said its protocol, smart contracts, infrastructure and official SDKs were unaffected. Its Guardian mechanism temporarily paused withdrawals and enabled the Security Council to return approximately 5M USDC to the affected trader. Withdrawals have resumed, and pending requests are being processed.

Market impact

Lighter has introduced wallet signature requirements for public pool transfers and made API key signatures non-public. It also plans to add IP allowlists, per-key permissions and limits, and proactive monitoring and revocation of API keys exposed to nonce reuse. The recovery addresses the affected account while the planned controls target the credential pathway behind the incident.

Related tokens
$USDC

Frequently asked questions

  1. How did the attacker exploit Lighter trading accounts?

    Lighter said nonce reuse in unofficial signing code used by certain accounts allowed API private keys to be derived from public signatures. The attacker then used a compromised account to extract assets through a public pool.

  2. Which parts of Lighter were affected by the security incident?

    The exploit targeted API credentials tied to certain trading accounts. Lighter said its protocol, smart contracts, infrastructure and official SDKs were unaffected.

  3. How much USDC was returned to the affected trader?

    Lighter's Security Council returned approximately 5M USDC to the affected trader through the platform's Guardian mechanism.

  4. What happened to withdrawals after the Lighter incident?

    Withdrawals were temporarily paused by the Guardian mechanism. Lighter then resumed them and began processing pending withdrawal requests.

  5. Which security changes has Lighter introduced or planned?

    Lighter introduced wallet signature requirements for public pool transfers and made API key signatures non-public. It plans IP allowlists, per-key permissions and limits, and proactive monitoring and revocation of exposed API keys.

Source attribution
Aggregated from WuBlockchain · Verified · Last refreshed 2h ago
Open original →