Sorry, to prevent abuse of free resources, accounts that hav
Lighter released an explanation of the November 16 security incident, stating that an attacker exploited a nonce-reuse vulnerability in unofficial signing code to derive API private keys and transfer assets. After the platform’s Guardian mechanism was triggered, withdrawals were suspended. The security committee has returned approximately 5 million USDC to affected users, and withdrawals have now resumed.
Incident Timeline
- [11-16 19:16] Lighter released a follow-up statement on the security incident: approximately 5 million USDC had been returned to affected users, and platform withdrawals had resumed (Wu Says)
- [11-17 00:02] Approximately 5 million USDC had been returned; Lighter resumed withdrawals and explained the cause of the security incident (Odaily Planet Daily)
Background and Impact
According to reports by Wu Says and Odaily Planet Daily, Lighter released a statement about the security incident on November 16, 2026. The incident occurred on the morning of November 16 UTC. The attacker exploited a nonce-reuse vulnerability in unofficial signing code to derive API private keys from public signatures, thereby taking control of victim accounts. After gaining control of the accounts, the attacker used a victim account to create a public pool, transferred funds into it, and then used an account under their control to redeem shares in the pool and transfer the assets. Following the incident, the Guardian mechanism in Lighter’s smart contracts was triggered, and the platform temporarily suspended withdrawals. Lighter’s security committee subsequently returned approximately 5 million USDC to affected traders. Withdrawals have now resumed, and pending withdrawal requests are being processed.
The two reports differ in how they describe the scope of the impact. Wu Says stated that “some trading accounts” were affected, while Odaily Planet Daily said that “one trader’s” account was affected. The reports also characterized the triggering of the Guardian mechanism differently: Wu Says called it “the incident triggering the smart contract Guardian protection mechanism,” while Odaily described it as “the Guardian mechanism being triggered abnormally.” Lighter emphasized in its statement that its protocol, smart contracts, and infrastructure were unaffected, and that the official SDK did not have this issue. The vulnerability stemmed from some users’ use of insecure, unofficial signing code.
The incident highlights the security risks associated with API keys and unofficial signing code. Users trading on various platforms—whether downloading the registration app for Binance, Gate.io, Bitget, Huobi HTX, or OKX—should be alert to the risk of private key exposure from unofficial tools. To prevent similar incidents from happening again, Lighter now requires wallet signatures for transfers to public pools and has made API key signatures private. The platform also plans to introduce IP allowlists, API key permissions and limits, and proactively monitor and revoke keys at risk of nonce reuse to further strengthen its security measures.
Frequently Asked Questions
### Were Lighter’s protocol and smart contracts damaged in this incident?
No. Lighter explicitly stated that its protocol, smart contracts, and infrastructure were unaffected, and that the official SDK did not have this vulnerability. The issue was with unofficial signing code used by users.
### What is being done with the affected users’ funds?
Lighter’s security committee has returned approximately 5 million USDC to affected traders. Platform withdrawals have now resumed, and pending withdrawal requests are being processed.
### What security measures will Lighter take next?
The platform now requires wallet signatures for transfers to public pools and has made API key signatures private. It also plans to introduce IP allowlists, API key permissions and limits, and proactively monitor and revoke keys at risk of nonce reuse.