
GoPlus Security 🚦 · 2026-11-17 02:43 UTC
#Lighter Incident Breakdown: Nonce Reuse in Custom Signing Code Enabled API Private Key Recovery 1️⃣ Affected Accounts An attacker derived the API private keys for two trading accounts on Lighter and used them to move funds out of those accounts. Approximately $15.48M was reportedly affected, with around $5M in USDC recovered and returned to the affected trader by the Lighter Security Council. Reported affected accounts: Account 1: Lighter Account ID: 714710 Associated onchain address: 0x0d1D09312665D31Ed68231b88079a245E0458F6F Amount affected: ~$10.39M Account 2: Lighter Account ID: 714723 Associated onchain address: 0x66Cf2f85115CC20bF439720927C1f93De9672068 Amount affected: ~$5.09M 2️⃣ Root Cause The affected accounts used insecure, unofficial signing code that reused cryptographic signing nonces across different transactions. This allowed the attacker to derive the API private keys from publicly available signatures. Lighter said its protocol, smart contracts, and official SDKs were unaffected. The attacker moved the funds through the following sequence: Create a public pool using the compromised account → Mint pool shares to an attacker-controlled account → Transfer the victim’s funds into the pool, increasing its net asset value (NAV) without issuing corresponding shares to the victim → Redeem the attacker’s shares and withdraw the funds. 3️⃣ Funds Withdrawn The attacker withdrew approximately 10.39M USDC from Lighter and swapped the proceeds for ETH. Onchain tracing identified part of the proceeds moving through multiple wallets to buy XMR1 on Hyperliquid. XMR1 should not be conflated with native Monero ($XMR). The available evidence does not establish that these purchases drove up Monero’s price. 4️⃣ Reported Attacker Account and Address Lighter Account ID: 769455 Associated onchain address: 0xb3fffca23d4444eE73349825ACD84f7b5020e387 🛡️ Security Recommendations ▪️ Use Lighter’s official Python, Go, or TypeScript SDKs, or its Agent Kit. Avoid implementing your own signing logic. ▪️ Let the official signer handle cryptographic signing nonces. Never reuse a signing nonce or substitute timestamps, counters, weak random values, or cached values. Signing nonces are distinct from transaction nonces. ▪️ If your code may have reused signing nonces, revoke and replace all related API keys immediately. Fixing the code alone isn’t enough. ▪️ Enable IP allowlisting and per-key permissions and limits as they become available. Separate permissions for trading, transfers, pool creation, and redemptions wherever supported. ▪️ Lighter now requires wallet signatures for transfers into public pools and no longer exposes API signatures publicly.
Loading the story on Tree News…