
Binance Just Paid Out $6.3 Billion — Why Did On-Chain Self-Custody Still Fail at Lighter?
On the early morning of November 16, decentralized perpetual contract exchange Lighter hit the emergency pause button, freezing withdrawals and liquidity pool creation across the platform. Although hackers did not exploit a single line of smart contract code, they drained approximately $15.5 million in USDC from two maker accounts within just a few minutes.
Zero code vulnerabilities, yet the vault was still emptied.
Just half a month earlier, on October 30, the world's largest centralized exchange, Binance, had just endured an industry-shaking coin theft incident where its hot wallet was drained of digital assets worth approximately $6.34 billion. In just eighteen days, both a centralized giant and a decentralized newcomer fell one after another.
Zero-fee liquidity pools became the hacker's hidden withdrawal gateway
At 10:11 UTC on November 16, on-chain tracking firm Bitquery detected unusual activity in two large maker accounts, numbered 714710 and 714723. The platform's native token, LIT, subsequently plummeted by over 17% within 24 hours.
Under Lighter's original permission rules, API keys could only be used for trading and internal transfers between associated wallet accounts; withdrawing directly to unfamiliar external addresses required signing with the wallet's master private key. However, the attacker first liquidated all contract positions in the victim account and consolidated them into USDC. They then used the compromised account to create a zero-fee public liquidity pool, followed by depositing approximately $10,000 from another personal wallet into this newly created pool and taking 99.99% of the shares. Next, they manipulated the maker account to pump funds into the pool at a rate of $1 million per transaction, and finally redeemed their shares directly, bypassing the withdrawal signature verification, and withdrew $10.39 million in USDC to the Ethereum mainnet.
The hacker transformed compliant business features into extraction pipelines.
Within four minutes, these funds were swapped for 5,764 ETH via CoW Swap. Of that amount, 1,600 ETH were distributed across ten new wallets and routed to another decentralized exchange, Hyperliquid, to purchase privacy coin XMR, while the remaining 4,165 ETH stayed in the mainnet address. Meanwhile, approximately $5.09 million in USDC intended for transfer from another account was promptly blocked after triggering the platform's Guardian security mechanism. Later that day, the security committee recovered the nearly $5 million fund and restored withdrawals.
Post-incident analysis pointed to a low-level engineering flaw: the third-party signing code used by market makers reused cryptographic nonces, enabling the hacker to reverse-engineer the API private keys directly from publicly available on-chain signatures.
A fake recruitment drive pried open Binance's internal signing infrastructure
Attackers linked to the North Korean hacking group TraderTraitor posed as recruiters, luring a core wallet engineer at Binance to download malware during a fraudulent interview.
After infiltrating the engineer's development environment, the malware replaced the local Python virtual environment tool pyenv, tracing its way to gain access to internal AI tools and the wallet infrastructure team, and subsequently taking over the internal signing service. According to Binance's preliminary investigation report released on November 3, hackers struck simultaneously across multiple public chains on October 30, draining 18,270 BTC, 970,500 SOL, and 44.2 million OP tokens from Binance's hot wallets. Notably, they even abused the EIP-7702 account abstraction authorization mechanism on the Ethereum network to submit 50 signed transactions, delegating execution rights for some hot wallets to external malicious smart contracts. Because the compromised hot wallets utilized a multi-party computation architecture, the Binance team lacked a single private key to unilaterally revoke the on-chain delegation. Simply shutting down server withdrawal APIs could not stop the already active contract authorizations on-chain. Ultimately, by coordinating with issuers and partners, they froze and intercepted approximately $2.85 billion in assets, and personally funded the recovery, bringing the reserve ratio for affected tokens back above 98% before October 31.
After Assets Go On-Chain, Permission Granularity Becomes the Life-and-Death Line
For years, a persistent notion in the industry has been that simply moving assets from centralized exchanges to decentralized protocols completely eliminates custody risk.
However, the core defense of centralized exchanges lies in the isolation between employee endpoints and hot/cold wallets. If a laptop belonging to a core engineer is compromised by phishing software, attackers can still bypass traditional risk controls by leveraging the new features of on-chain account abstraction, even when multi-party computation signing is employed.
On-chain self-custody also has its own Achilles' heel.
While decentralized exchanges lock asset settlement into smart contracts, they hand over account fund management to off-chain API keys in pursuit of high-frequency trading experiences. Once market makers cut corners by using unreviewed third-party signing scripts, or if the protocol fails to list public liquidity pool transfers on the high-risk withdrawal allowlist, hackers can directly plunder accounts. The emergency patch deployed by Lighter post-incident directly exposed the crux of the issue: the platform now mandates that transfers to public liquidity pools must be signed by the main wallet, and has introduced API key IP whitelisting and fine-grained permission isolation.
For institutions and traders placing substantial funds on-chain or at exchanges, passing a code audit is merely the starting point of security work. What truly determines the safety of principal capital is whether signing devices are physically isolated and whether API permissions are strictly confined solely to trading operations.















