A hot wallet does not get drained by a clever contract. It gets drained by a key that signs something it should not.
That is the uncomfortable shape of what happened to Binance on October 29 and 30, 2026, Beijing time. The publicly reported numbers move by the hour: $2.5 billion, $3.3 billion, $3.5 billion, and a wider multi-chain tally near $5.7 billion. Most of those are estimates of outflows, not confirmed losses. What follows is what we could verify ourselves against Ethereum mainnet, with transaction hashes you can open.
The four minutes that matter
At 04:20:59 Beijing time on October 30 (20:20:59 UTC on October 29), a transaction from an address we will call the operator, 0x7c8601d4645b93cea45f71e118a729332e6b5ca0, submitted 50 EIP-7702 authorizations in a single batch. Every one of them delegated the same account, the wallet labeled Binance 14 (0x28C6c06298d514Db089934071355E5743bf21d60), to the same contract, 0x63e842b054bd624a465454d533c33f573e9c6fae.
We recovered the signer from each authorization signature. All 50 recover to Binance 14. The signatures are distinct, the nonces are sequential, and the batch consumed nonces 18,914,775 through 18,914,824. In plain terms: the compromised key did not just delegate once. It burned 50 nonces in one shot, which has the side effect of invalidating any lower-nonce transaction that might already have been signed for that wallet.
Four minutes later, at 04:24:23 Beijing time, the operator called Binance 14 directly. Transaction 0x53bd38b816c23e74134786c29a8c18d792777998a3b9326047b583100e88e2f3 executed under the delegated code and swept:
- 167,464.24785655882 ETH to
0x5227f603c1ee34ce3c06efe6477003bdfccb2f8c - 1,615,409,498.97 USDT
- 64 token-transfer logs in total, covering more than 60 assets, including 29,934 wBETH, 11,372 XAUt, 62.6 million RLUSD, 27.8 million USD1, 198 million ENA, 7.17 trillion PEPE, 2.26 million LINK, 127,853 AAVE, 6.19 million UNI, 82.5 WBTC and 1,898 PAXG
Seconds later, a second Binance-labeled wallet, Binance 16 (0xdfd5293d8e347dfe59e90efd55b2956a1343963d), sent 28,005.6 ETH to the same receiver in transaction 0x51f263fa50966df6bbd7f8c6e6e99e3791c94444f7c4343b2fef1ee2d62fd39f. The receiver then consolidated 195,460 ETH into 0x8532fa14acaf483729c449b8458aeddb900543d4, a fresh address that still holds it.
This matches the timeline circulating since the early hours: delegation at 04:20, sweep at 04:24, secondary transfers from 04:32, stablecoin freezes from 05:04.
The operator was not funded from nowhere. Its address received three internal transfers of roughly 0.098 ETH each from the Tornado Cash 0.1 ETH pool, starting about 37 hours before the sweep and totalling about 0.294 ETH. That is consistent with a deliberately funded, purpose-built operation rather than an opportunistic sweep, though Tornado Cash itself is a privacy tool and says nothing on its own about who is behind the address.
Why EIP-7702 makes this worse
EIP-7702, shipped with Ethereum’s Pectra upgrade, lets an externally owned account attach smart contract code to itself. The mechanism is cleanly described in the EIP: an authorization tuple sets the account’s code to 0xef0100 || address, a pointer to the delegate. From then on, calls to the wallet execute the delegate’s logic with the wallet’s own authority.
We checked the code pointer directly. At block 26,300,753, Binance 14’s code read 0xef010063e842b054bd624a465454d533c33f573e9c6fae. Today it reads 0x, meaning the delegation was later cleared. The window in which it existed was enough.
Two properties matter for anyone trying to understand the damage:
First, this is not an approval. An ERC-20 allowance lets a contract move a specific token up to a specific amount. A 7702 delegation lets the delegate act as the account and reach everything the account controls, in one transaction. That is why a single call could produce 64 token transfers across more than 60 assets without a single approval prompt.
Second, the authorization must be signed by the account being delegated. As the EIP states, the authorization is only valid for the chain and nonce it names, but it is a signature by that account’s key. A malicious website cannot delegate your wallet without your signature, and an attacker cannot forge Binance 14’s authorization without material that lets them sign as Binance 14.
The practical conclusion is narrow and uncomfortable: whatever the entry point, the attacker could sign for a live exchange hot wallet. Whether that came from a leaked private key, a compromised signing service, or someone inside the operational path is not public. Binance has not said.
The freeze line, and where it stops
Stablecoin issuers responded within the hour. Circle froze 823,000,000 USDC, a figure we confirmed both from the receiver’s balance and from the contract’s blacklist flag for 0x5227...b2f8c, which returns true. Tether’s CEO Paolo Ardoino said the company froze more than 1.567 billion USDT; the same receiver still holds 1,175,464,712.78 USDT as of our check.
That asymmetry is the part users consistently misread. Frozen is not recovered. It means the tokens cannot move, not that they are back in the exchange’s treasury. And the freeze only reaches issuer-controlled assets. The 195,460 ETH sitting at the secondary address is native ether. No company can blacklist it.
So the current picture is a standoff: roughly 2.4 billion dollars of stablecoins immobilised, 195,460 ETH parked in a wallet that has not moved, and a recovery path that depends on law enforcement, exchange cooperation, or an operational mistake by whoever holds the keys.
What Binance has said, and what it has not
Binance’s public line has been consistent on one point: user funds are safe. The company told TechCrunch it was “aware of reports of a potential security issue” and that “user funds are completely safe”, and a spokesperson confirmed withdrawals were temporarily suspended on multiple networks as a precaution. CZ, still the largest shareholder, wrote on X that the exchange had likely been hacked and that he expected user funds to be “fully covered”. Co-founder Yi He said the team was investigating and emphasised user safety.
None of those statements include a root cause, a loss figure, or a reconciliation of what left versus what was frozen. The SAFU reserve exists for exactly this kind of event, but whether it will be drawn on, and by how much, has not been confirmed.
Independent estimates vary because they count different things. A single Ethereum wallet sweep is not the same as all outflows from all Binance-labeled wallets across Ethereum, BNB Chain, Tron and Bitcoin. Some tallies include internal transfers that may not be theft. Until Binance publishes an address list and a reconciliation, every total is an upper bound with a wide error bar.
If you hold funds on an exchange
The useful lessons are boring, which is why they get skipped.
- Counterparty risk is not theoretical. A hot wallet is online by design, because it has to sign withdrawals. That convenience is the attack surface. Keep trading balances small and move the rest to self-custody.
- Watch for the second wave. Large hacks produce fake “recovery”, “refund” and “verification” sites within hours. No legitimate exchange will ask you to connect a wallet, sign a 7702 authorization, or pay a release fee. Our guide to crypto recovery scams covers the playbook.
- Read delegation prompts. If a wallet or dapp asks you to authorize account code, that is not a login and not a claim. It is handing over your account’s execution rights. The EIP-7702 phishing guide walks through what those prompts look like.
- Understand what “frozen” means for you. If you held USDT or USDC on Binance, issuer freezes may help the exchange recover part of the balance sheet. If you held ETH or BTC, the recovery path is slower and less certain.
Bottom line
The technical story is not a clever exploit of a new Ethereum feature. It is the oldest failure in the book, wearing new clothes: a key that should never have signed, signed 50 times.
EIP-7702 made the consequence faster and broader. One delegation turned a hot wallet into an attacker-controlled contract account, and one transaction emptied more than 60 assets. The freeze line stopped roughly 2 billion dollars of stablecoins. It could not touch the ether.
Until Binance publishes a real post-mortem, treat the totals as estimates, the assurances as commitments, and your exchange balance as a counterparty exposure rather than a deposit box.
Frequently Asked Questions
How much did Binance lose in the October 2026 hack?
There is no confirmed figure. On-chain data verified for this article shows 167,464.24785655882 ETH and 1,615,409,498.97 USDT leaving one wallet in one transaction, plus dozens of tokens and at least 28,005.6 ETH from a second wallet. Reported estimates range from about $2.5 billion to $5.8 billion depending on which chains and wallets are counted. Binance has not published a loss figure.
What is EIP-7702 and why does it matter here?
EIP-7702 lets a regular Ethereum account attach smart contract code to itself by signing an authorization. The delegated code then executes with the account's full authority, which is far broader than a token approval. Setting the delegation requires a valid signature from the account's own key, so this incident points at key or signing-system compromise rather than a contract vulnerability.
Can stolen ETH be frozen like USDT and USDC?
No. Stablecoin issuers can blacklist addresses and freeze their own tokens, which is why roughly 2 billion dollars in USDT and USDC stopped moving. ETH, BTC and other native assets have no issuer that can freeze them. 195,460 ETH was consolidated into a fresh address and remains outside the reach of issuer blacklists.
Are Binance user funds safe?
Binance says user funds are completely safe and that withdrawals were suspended on multiple networks as a precaution. It has not published a root-cause analysis or a confirmed loss number. Treat the statement as a commitment, not an audited fact, and keep only working balances on any centralized exchange.