On Thursday evening, 29 October, a Binance hot wallet on Tron sent 612.7 million USDT and 46.4 million TRX to an address the exchange didn't control.It took less than two minutes. Ethereum followed. So did Bitcoin, Solana, Optimism, and five other chains. By the time Binance paused withdrawals that night, an attacker had moved roughly $6.36 billion out of Binance wallets on ten blockchains, most of it in about 20 minutes, according to TRM Labs.Nothing in crypto's history comes close. The previous record belonged to Bybit for just over 20 months, and the FBI put that theft at $1.5 billion, a little under a quarter of this one."It's the biggest hack in history."Aravind Srinivasan, head of the systematic OTC business at market maker GSR, quoted by RTÉThe size of the number isn't what kept me reading, though. This line from Binance did: the exchange said it had "found no evidence of any wallet private key leak." Every one of those transfers was validly signed. Bitcoin, Ethereum and Tron did exactly what they were built to do.So how do you lose $6.3 billion without losing a key?How an exchange actually holds your coinsA blockchain accepts any transfer that carries a valid signature for the sending address. It has no way to tell whether that signature came from the rightful owner or from someone who has taken over the process that produces it. Hold on to that point; the whole story turns on it.Large exchanges keep most customer assets in cold storage (offline, and slow to move on purpose) and a smaller float in hot wallets, which sign automatically so your withdrawal clears in seconds. "Smaller" is relative. Binance held about $144 billion in custody before the attack, so this loss works out to roughly 4% of it.A hot-wallet signer is, by design, an obedient machine. A request comes in, passes a policy check, and gets signed. The key itself sits in a hardware security module (HSM) or a multi-party computation (MPC) setup and never leaves. That keeps the key safe from theft. Whether each incoming request deserves a signature is a separate problem, and a harder one.Step one: a DevOps engineer's laptopBinance's first explanation was that the incident "may involve a compromised DevOps engineer's laptop," which let the attacker reach an internal service container able to submit withdrawal transactions.The story grew the next day. Co-CEO Richard Teng said investigators had found additional intrusion points, that the attacker used a self-destruct mechanism to erase tools and traces, and that Binance is now reviewing endpoints, cloud systems, key management and signing processes across the whole company. It still hasn't said how the laptop was compromised."It involved a more complex attack process."Binance co-CEO Richard Teng, in a post on X reported by ForbesIf that sounds familiar, it should. The Bybit theft also started on a developer's machine: attackers got into Safe{Wallet}'s environment and replaced a JavaScript file so that Bybit's signers approved a transaction they couldn't see clearly. Attackers who target crypto firms have spent years luring crypto developers into fake job interviews whose "coding tests" install malware. Nobody has confirmed that's what happened at Binance. It's the obvious first place to look.Step two: fifty signatures and one walletOn Ethereum, the attacker used EIP-7702, a feature that went live with the Pectra upgrade on 7 May 2025. It lets an ordinary wallet (an externally owned account, or EOA) point to smart-contract code and run that code as if it were its own. Wallet teams wanted it for batched transactions and sponsored gas fees. Turning it on needs exactly one thing: a signature from the wallet's own key.At 20:20:59 UTC, the attacker submitted a single transaction carrying 50 EIP-7702 authorizations, all signed by the hot wallet labeled Binance 14. Each authorization is tied to the account's nonce, a counter that goes up by one with every transaction. A busy exchange wallet's nonce moves constantly, so the attacker prepared 50 consecutive ones; whichever matched at the moment of submission would work. One did.That authorization pointed Binance 14 at a sweeper contract that took orders only from the attacker. Three minutes and 24 seconds later, the wallet sent out 167,464 ETH and 63 tokens, including 1.615 billion USDT. The delegation stayed in place afterwards, so customer deposits that kept landing at the same address were swept six more times over the next three and a half hours.Two details matter here. “Fifty sequential signatures” means sustained access to the signing path, well beyond one phished approval. And Teng has said the delegation bypassed Binance's usual approval process; the signer produced something its own policy layer never reviewed.The technique itself wasn't new. A month after Pectra shipped, Wintermute found that more than 80% of EIP-7702 delegations pointed at copy-pasted sweeper contracts that drain wallets with leaked keys. A December 2025 arXiv paper on EIP-7702 phishing showed that one malicious authorization can hand an attacker persistent control of an account. The Binance attacker ran the same playbook at exchange scale, with Binance's own signer doing the signing.Security researcher Taylor Monahan made the key point back in 2025, when those sweeper delegations first spread:"It's not actually a 7702 issue."Taylor Monahan, speaking to The Block about wallets drained through EIP-7702 (June 2025)The feature only does what a valid signature tells it to. The weak point is whoever controls the signing.Why "no key leaked" is cold comfortTRM's reading of the chain data points the same way. It saw ordinary signed transfers leave Binance wallets on several chains, across different key types, within minutes, and concluded that the attacker could make Binance's hot-wallet signing infrastructure authorize transfers of its choosing.That's why Binance's reassurance doesn't reassure me much. If an attacker can submit requests from inside the trusted zone, or quietly edit the checks those requests pass through, the HSM can stay sealed and still sign away the balance. Binance's statement is very likely true. It answers a different question from the one customers are asking. Fireblocks, which builds custody infrastructure, put the practical rule well: treat any signature produced outside your signing platform as an incident.The race to freeze the moneyThe response was fast, at least for some assets. Within about an hour, Tether had frozen 975.1 million USDT and Circle 823 million USDC in the main receiving wallet, roughly $1.8 billion between them; Circle said it acted in coordination with law enforcement. Tether's total later rose to more than 1.567 billion USDT. Binance now puts everything frozen across issuers and partners at around $3 billion."In coordination with law enforcement, we have frozen more than 800M USDC."Circle CEO Jeremy Allaire, posting on X, via DecryptThe attacker clearly knew the clock was running. TRM traced about 325 million USDT sold through UniswapX and other intent-based contracts for roughly 122,300 ETH. That implies about $2,650 per ETH at a time when ether traded between $2,300 and $2,350; paying a premium of more than 10% is what urgency looks like on-chain. A second wallet deposited 60 million USDT into Aave and borrowed about 19,760 ETH against it before Aave froze the affected markets. By Bitquery's count, the attacker's ether pile has since grown to 490,361 ETH, mostly from converting stablecoins.There's an awkward lesson in that split. The most centralized assets in crypto, dollar stablecoins with an issuer who can blacklist an address, clawed back close to half of the loss within hours. BTC and ETH have nobody to call. Even a freeze isn't the end of it: TRM's Ari Redbord points out that getting frozen funds back requires a separate legal process.Who is behind itNobody has been officially named. As of 31 October, no government has publicly attributed the attack, Binance hasn't named a suspect, and its root-cause findings aren't out yet. Analytics firms have shared early assessments based on on-chain patterns; until law enforcement or Binance's post-mortem confirms anything, I'm leaving the question open.What the chain data does show is planning. According to TRM, preparation began at least 36 hours before the theft: the attacker's wallets were funded through the Tornado Cash mixer, and transaction signatures were collected in advance. Whoever did this was patient, and had deep access long before the first coin moved.What Binance has promisedBinance says it will cover every loss with company money. It has reserved more than $6.34 billion, about $5 billion of it already held in the same tokens that were taken, and is buying the rest on the market and over the counter. Its emergency SAFU fund alone is worth roughly $1.17 billion.Withdrawals are still paused. Binance's 31 October update targets a phased restart within about 34 hours, subject to security checks, and proof-of-reserves results by Monday, 2 November. A technical post-mortem is promised but has no date.What has to changeBybit's breach began on a developer's machine at a supplier; Binance's began on a DevOps engineer's laptop. Any laptop that can reach production deserves the protection production gets: a dedicated, locked-down device, credentials tied to a hardware key, access that expires when the task is done, and a firm rule against running code from strangers (that recruiter's "take-home assignment" included).Binance's signer trusted whatever its internal services handed it. A second approver, running on separate infrastructure that a hijacked container can't touch, should match every large withdrawal to a real customer request before anything is signed. Fireblocks makes a related point: hot-wallet keys should never be usable from a developer machine at all.EIP-7702 needs its own rules. A treasury wallet that suddenly delegates to contract code is about as loud a warning as custody gets, and it shows up on-chain for anyone watching. Exchanges should refuse to sign 7702 authorizations unless a human expects one, and a single request for dozens of them, one per upcoming nonce, should page someone immediately.Then there's containment. One intruder emptied wallets on ten chains in about 20 minutes, which tells me the signing paths shared far too much. Give each chain and wallet tier its own signer, cap how much value can leave per hour, and halt outflows to unfamiliar addresses automatically. Binance paused withdrawals at about 22:15 UTC, roughly two hours after the first transfers at about 20:05 UTC, and the hijacked Ethereum wallet kept sweeping new deposits even after that.If you hold funds on Binance, three things. Expect a wave of "refund" and "compensation" phishing; Binance will never ask for your 2FA codes or recovery phrase. When the proof-of-reserves report lands, use Binance's verification tool to check your balance is included. And once withdrawals reopen, ask yourself whether long-term holdings belong on any exchange at all.Four years ago I argued in Regulating Chaos that IoT security would only improve once the law caught up with its weakest devices. Crypto custody has reached the same point, and its weakest device turned out to be a laptop. Monday's reserves report will tell us whether Binance's customers are whole; the post-mortem will tell every other exchange which of its own engineers' desks to check first.Disclosure: I hold no position in Binance and have no affiliation with the company.