2026.11.02 · 5 min · security · backend · news
The $6.3B Binance hack: how one signature emptied a hot wallet.
On 29 October about $6.3 billion left Binance hot wallets, most of it in about 20 minutes. Binance says no private key leaked. On Ethereum, its own signer was made to sign an EIP-7702 delegation that let the attacker's code act as the wallet. The path in, the 50-nonce trick, and what it means for anything that signs. As of 2026.11.
On 29 October 2026, about $6.3 billion left Binance hot wallets on 10 blockchains, most of it in about 20 minutes from 20:05 UTC. It's the largest crypto theft on record. And by Binance's own account, nobody stole a private key. Attackers got Binance's signing system to sign one permission that said, in effect, "let this code act as me". That code then swept the wallet.
Watch the 60-second version on Instagram.
If you build web services, you know the pattern already: a valid signature from a trusted service you've broken into is worth more than a stolen password. This is that, at a $6B scale.
The numbers
Estimates differ by source: Binance says about $6.3B, TRM Labs $6.36B, Chainalysis about $6.4B. TRM's breakdown by chain:
| Chain | Taken |
|---|---|
| Ethereum-chain assets | $3.79B |
| Bitcoin (18,270 BTC) | $1.47B |
| Tron | $628M |
| XRP | $296M |
| Solana | $96M |
| Smaller chains | the rest |
Both TRM ("high confidence") and Chainalysis link it to TraderTraitor, a North Korean, Lazarus-linked unit. TRM points to the same playbook as Bybit in 2025; Chainalysis found the funds mixed on-chain with funds from the Bitget theft. That's attribution by blockchain analytics firms, not proof. Wikipedia reports an FBI alert dated 31 October naming North Korea, which I couldn't verify directly.
The way in
The prep started early. The attacker's wallet was funded from Tornado Cash at least 36 hours before. On the day, a "sweeper" contract was deployed and rehearsed on the attacker's own wallets, and the test funds were sent back.
Then the entry, in Binance's preliminary account: "a compromised DevOps engineer's laptop" gave access to "a service container" that submits withdrawals. Binance says there is "no evidence of any wallet private key leak". It has since reported "additional points of breach" without naming them, and a full post-mortem is promised.
The signer is the real target. It doesn't need to leak its key to be useful to an attacker; it only needs to sign what it's given. Binance co-CEO Richard Teng said the delegation "did not pass through Binance's normal approval controls".
One signature, 50 copies
On Ethereum, the attack used EIP-7702, live since 2025, which lets an ordinary account run a contract's code. An EIP-7702 authorization is [chain_id, address, nonce, y_parity, r, s]. It names code. It has no amount and no recipient.
// What the signer was tricked into signing (EIP-7702 authorization)
{ chainId: 1, address: SWEEPER_CONTRACT, nonce: 18914775 /* ...+49 more */ }
// No "to", no "amount": it means "my account now runs this code"One type-4 transaction carried 50 of these, all signed by the hot wallet "Binance 14", one for each of its next 50 nonces. Exactly one would match the wallet's current nonce, and that one set the wallet's code to 0xef0100 || sweeper. The code stays until it's changed.
The figure's position of the match is illustrative. What followed isn't: about 3.4 minutes later, a single sweep call took 167,464 ETH plus 63 tokens. The sweeper's execute function then used the wallet's control of a Binance smart account to pull 823M USDC.
The delegation stayed active for about 4 hours, so new deposits were swept again (21:04, 21:44 UTC and on). It was cleared at 00:10 UTC on 30 October by delegating to the zero address.
On the other 9 chains there was no delegation trick: these were ordinary signed transfers. That's why TRM thinks the signing infrastructure itself was compromised, not just one key.
What people get wrong
- "Hackers stole Binance's private keys." Binance says no key leaked. What failed was the system that decides what gets signed.
- "EIP-7702 is broken." Analysts find no flaw in EIP-7702 itself. It did exactly what it says: the account signed a delegation, so the account ran that code.
- "EIP-7702 is a multi-signature protocol." Teng called it that. It isn't; it's account delegation.
- "The money is gone." About $3B is frozen: Tether (about 1.77B USDT), Circle (about 825M USDC), Ripple and others. The BTC and ETH can't be frozen. Binance says it will cover all losses from SAFU and company funds.
On a client project I'd treat the signer as its own trust boundary: it should check what a request means (a delegation, a new recipient) against policy, not just that it came from the service allowed to ask.
The short version
- About $6.3B left Binance hot wallets on 29 October, most of it in about 20 minutes; analysts link it to North Korea's TraderTraitor.
- Binance says a compromised DevOps laptop reached the service that submits withdrawals, and no private key leaked.
- On Ethereum, the signer signed 50 EIP-7702 authorizations, one per upcoming nonce; the match made the hot wallet run the attacker's sweeper.
- One call swept 167,464 ETH plus 63 tokens, and the delegation kept sweeping deposits for about 4 hours.
- About $3B is frozen; BTC and ETH aren't. The root cause is still preliminary.
Sources: Binance, Security Incident Update · TRM Labs, North Korea steals USD 6.36B from Binance · Chainalysis, Binance exploit latest findings · Wikipedia, 2026 Binance hack · DEV / Panda Security, How EIP-7702 delegation emptied a hot wallet · CoinDesk, Binance uncovers wider breach · EIP-7702 specification