Binance just paid 6.3 billion, so why did Lighter's on-chain self-custody still fail?
Original headline币安刚赔六十三亿,Lighter 链上自托管为何照样失守
Not investment advice. Muhabbit scores how much a story may matter, not which way to trade.
Decentralized perpetuals exchange Lighter froze withdrawals and pool creation on Nov. 16 after attackers drained roughly $15.5 million USDC from two market-maker accounts without exploiting any smart contract flaw, instead abusing a zero-fee public liquidity pool to bypass withdrawal signature checks; the platform’s LIT token fell more than 17% in 24 hours. The stolen $10.39 million was swapped via CoW Swap into 5,764 ETH within four minutes, with 1,600 ETH spread across ten wallets and part routed to Hyperliquid for privacy coin XMR, while a separate $5.09 million transfer was blocked by Lighter’s Guardian mechanism and later recovered. The breach followed Binance’s Oct. 30 hot-wallet hack, in which attackers linked to North Korea’s TraderTraitor group stole 18,270 BTC, 970,500 SOL and 44.2 million OP after malware compromised an engineer’s device and internal signing service, forcing Binance to restore affected reserves to over 98%. Lighter traced its loss to a third-party signing script that reused cryptographic nonces, letting attackers derive an API private key from public on-chain signatures. The incidents show that self-custody and MPC signing do not eliminate key and permission risk, and the next test is whether Lighter’s patch—mandatory main-wallet signatures for pool transfers plus API key IP whitelisting and granular permission isolation—restores depositor confidence.
Muhabbit's AI wrote this summary in its own words from TechFlow's report and translated it from Chinese. It can get details wrong, so check the source.
Named in this story
Lighter, Binance, USDC, LIT, TraderTraitor