---
title: Lighter post-mortem: unofficial signing code reused nonces, exposing a trader's API keys; Security Council returned about $5M USDC and withdrawals resumed | ctxsec
url: https://ctxsec.com/items/lighter-security-incident-single-compromised-external-party-withdrawals-paused-nov-16
description: "Lighter's official post-mortem says that on the morning of November 16 an attacker gained control of a trader's API keys because the accounts' unofficial signing code reused signature nonces, which made the private keys recoverable from public signatures. Lighter says its protocol, smart contracts, infrastructure and official SDKs were not affected. The attacker created a public pool from the affected account, minted shares in a separate account, moved the trader's funds into the pool and redeemed them. Lighter's contract Guardian paused withdrawals, which it says allowed the Security Council to return about $5 million USDC; Guardian mode was then turned off and deposits and withdrawals resumed the same day. Lighter has not given a total amount taken. On-chain analysts' earlier figure of about $15.5 million across two accounts remains unconfirmed by Lighter."
status: "official (Lighter X article 'Signing Safely on Lighter: Lessons from November 16' and follow-up posts, Nov 16, 2026); Lighter has not published a total-loss figure, last updated Nov 19, 2026, 12:45 PM ET"
published: 2026-11-16
updated: 2026-11-19T12:45:00-05:00
---

> Lighter's official post-mortem says that on the morning of November 16 an attacker gained control of a trader's API keys because the accounts' unofficial signing code reused signature nonces, which made the private keys recoverable from public signatures. Lighter says its protocol, smart contracts, infrastructure and official SDKs were not affected. The attacker created a public pool from the affected account, minted shares in a separate account, moved the trader's funds into the pool and redeemed them. Lighter's contract Guardian paused withdrawals, which it says allowed the Security Council to return about $5 million USDC; Guardian mode was then turned off and deposits and withdrawals resumed the same day. Lighter has not given a total amount taken. On-chain analysts' earlier figure of about $15.5 million across two accounts remains unconfirmed by Lighter.

[← Cybersecurity News](/news) · [markdown](/items/lighter-security-incident-single-compromised-external-party-withdrawals-paused-nov-16.md)

official (Lighter X article 'Signing Safely on Lighter: Lessons from November 16' and follow-up posts, Nov 16, 2026); Lighter has not published a total-loss figure

2026-11-16 7:34 AM ET · updated

Nov 19, 2026, 12:45 PM ET

### Lighter post-mortem: unofficial signing code reused nonces, exposing a trader's API keys; Security Council returned about $5M USDC and withdrawals resumed

- **Already shipped:** a wallet signature is now required to move funds into a public pool, so an API key alone cannot repeat this path, and API-key signatures are no longer public.
- **Still coming:** IP allowlists, per-key permissions and limits, and monitoring that voids keys showing nonce reuse.
- **Traders:** sign only with an official Lighter SDK (Python, Go, TypeScript or the Agent Kit). If you used other signing code, rotate every API key. Lighter identified `0xb3fffca23d4444eE73349825ACD84f7b5020e387` as the wallet it believes is associated with the attacker.

Sources: [Lighter official X article: Signing Safely on Lighter: Lessons from November 16 (Nov 16, 2026)](https://x.com/Lighter_xyz/status/2122394446343946717) · [Lighter on X: deposits and withdrawals back to normal after Guardian Mode deactivated (Nov 16, 2026)](https://x.com/Lighter_xyz/status/2122394646164758654) · [Lighter on X: leaked API key for a specific trader's account; protocol and contracts unaffected; Guardian mode enabled (Nov 16, 2026)](https://x.com/Lighter_xyz/status/2122311006604984497) · [Lighter on X: security incident involving a single compromised external party; withdrawals and pool creation suspended (Nov 16, 2026)](https://x.com/Lighter_xyz/status/2122284181422284986)
