Lighter Releases Security Incident Statement: API Key Leak Led to User Fund Theft, About $5 Million in USDC Recovered
November 17: Lighter officially released a security incident statement saying that an attacker stole funds by obtaining leaked API keys from traders. The incident was not caused by vulnerabilities in the Lighter protocol, smart contracts or infrastructure; instead, the affected accounts used unofficial signing code that reused signing nonces (Nonce), allowing the attacker to derive the API private key from publicly available signing data.
Lighter said that the signing code of the affected accounts reused nonces, enabling the attacker to compute the relevant API keys without accessing the accounts or Lighter's systems, and to use the leaked keys to create public liquidity pools, move account funds and redeem withdrawals.
After the incident, Lighter's smart contract Guardian mechanism detected the anomaly and was triggered, temporarily pausing withdrawals. Subsequently, the Lighter Security Council helped recover approximately 5 million USDC for the affected traders. Guardian mode has now been turned off, withdrawals have resumed, and all pending withdrawals are being processed one after another.
Lighter stressed that its official Python, Go and TypeScript SDKs as well as the Agent Kit all use secure random number generation mechanisms and were not affected by this issue. The platform also plans to roll out security measures such as API key IP whitelisting and permission and trading limit configurations, and to strengthen monitoring of nonce reuse.
Lighter recommends that users of automated trading or agents adopt the official SDK; if custom or third-party signing code is used, they should ensure that every signature uses a cryptographically secure random number generator, and rotate API keys promptly when it is not possible to confirm whether a nonce reuse risk exists.