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
0xb3fffca23d4444eE73349825ACD84f7b5020e387as 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) · Lighter on X: deposits and withdrawals back to normal after Guardian Mode deactivated (Nov 16, 2026) · Lighter on X: leaked API key for a specific trader's account; protocol and contracts unaffected; Guardian mode enabled (Nov 16, 2026) · Lighter on X: security incident involving a single compromised external party; withdrawals and pool creation suspended (Nov 16, 2026)