Fifty Pre-Signed Authorizations Drained $6.3 Billion From Binance. No Private Key Was Stolen.

In short
Key takeaways
- About 6.36 billion dollars left Binance wallets on ten chains starting at 20:05 UTC on 29 October 2026, most of it within twenty minutes.
- Binance says there is no evidence of a private key leak; TRM and Elliptic describe a compromise of the signing infrastructure around the wallets.
- On Ethereum the attacker sent 50 pre-signed EIP-7702 authorizations so one would match the hot wallet's moving nonce, then delegated it to an attacker-controlled sweeper.
- The single sweep moved 167,464 ETH and 63 tokens including 1.615 billion USDT, and the attacker swept new deposits repeatedly through the evening.
- Binance 14 and Binance 16, the emptied wallets, appear in Binance's 1 October proof-of-reserves report, and the roughly 204,500 ETH taken is about 5.6 percent of its ether reserves.
At 20:05 UTC on 29 October, money started leaving Binance. The first transfers were on Ethereum. Within twenty minutes the attacker had moved assets on ten blockchains. By the time the exchange suspended withdrawals, about 6.36 billion dollars had left wallets it controlled. It is the largest crypto theft on record, roughly four times the 1.5 billion dollar Bybit hack of February 2025.
The size is the headline. What makes this incident worth studying is that the cryptography worked. Binance says it found no evidence of a private key leak. The attacker did not break elliptic curve signatures. They compromised the system that decides what to sign, then used a feature designed to make wallets more flexible to turn one of Binance's hot wallets into a machine that swept funds to an address only they controlled.
The keys were not the problem
A hot wallet is an internet-connected wallet an exchange uses to process withdrawals. It signs constantly, which is why it is the most exposed part of an exchange's custody stack. Binance's statement says there is no evidence of a private key leak. Elliptic's assessment is that the attacker compromised "the infrastructure and people around the wallets," not the cryptography.
TRM Labs goes further. Its assessment is that the attacker gained the ability to make Binance's hot-wallet signing system sign transactions of their choosing across chains. The evidence is the pattern: wallets on ten chains, with different key types and signing schemes, all produced valid signatures for the attacker inside roughly thirty minutes. A single leaked key does not explain that.
The failure was operational. The math held; the approval path did not.
Fifty signatures and a moving nonce
The Ethereum leg is the most technically interesting. EIP-7702 arrived with the Pectra upgrade in May 2025. It lets an ordinary wallet, an externally owned account, sign an authorization that makes it execute a smart contract's code. The feature exists to support batching, gas sponsorship, and smart-account behaviour. In this attack it did exactly what it was designed to do.
The attacker prepared 50 signed authorizations, each pointing the wallet at a sweeper contract that accepted instructions only from the attacker. The reason for 50 is the nonce. A wallet's nonce is its running transaction count, and a hot wallet processes a steady flow of withdrawals, so the nonce keeps moving. A single pre-signed authorization would likely be stale by the time it landed. Fifty gave the attacker a spread of nonces, and one eventually matched.
When it did, the wallet was delegated to the sweeper. Three minutes and 24 seconds later, the attacker instructed it to send its entire balance to an attacker-controlled address. That single transaction moved 167,464 ETH and 63 tokens, including 1.615 billion USDT.
The attacker was not done. New deposits kept arriving at the wallet, and the sweeper kept collecting them: 20:41, 20:59, 21:04, 21:44, 22:39 and 23:56 UTC. A second Ethereum hot wallet sent 174 million dollars directly to the attacker. In total, about 204,500 ETH left Ethereum wallets, worth roughly 442 million dollars at the time.
Ten chains, one evening
Ethereum was the clever part. The rest was ordinary. On Bitcoin, a Binance hot wallet sent just over 18,270 BTC to an attacker address in eleven transactions, all in block 973,732. On Tron, a hot wallet sent 612.7 million USDT and 46.4 million TRX. The other chains in the sweep include the XRP Ledger, Solana, Arbitrum, Avalanche, Optimism, Base and Polygon.
The preparation started at least 36 hours before the theft. The operational wallet was funded through small Tornado Cash withdrawals. The attacker deployed and tested malicious code on three wallets before going live. TRM and Elliptic both describe a self-destruct mechanism that destroyed tooling and traces as the attacker moved, which is part of why the reconstruction is still provisional.
The initial vector is the least settled part. Binance's co-CEO Richard Teng said the incident may have involved a compromised DevOps engineer's laptop, giving access to a service container and then to unauthorised withdrawal transactions. He described it as a complex process rather than a single click, and said the investigation had not attributed responsibility to any individual. Binance later said it found additional points of breach. Analysts at Blockaid and TRM point to social engineering, the fake recruiter or coding-test lure that has been used against crypto employees since at least 2020 and that CISA has warned about in its TraderTraitor advisories.
The proof-of-reserves contradiction
Binance says the attack hit its own hot wallet, not customer funds, and that user funds are safe. It says it set aside about 6.34 billion dollars of company funds, including 5 billion already held in the affected cryptocurrencies, and would cover the rest through the market and over-the-counter purchases. The shortfall is covered by SAFU, the exchange's emergency reserve, and company money.
CoinDesk then looked at Binance's own reserve data. The wallets that were emptied, Binance 14 and Binance 16, are the same wallets Binance lists in its monthly proof-of-reserves report as backing customer balances. The 1 October report showed Binance 14 holding 89,475 ETH and 1.26 billion USDT among 37 assets. Binance held almost exactly enough ETH to cover customers, with essentially no surplus. The roughly 204,500 ETH taken is about 5.6 percent of its ether reserves, which leaves ether backing near 94 percent until the exchange replaces what was stolen. Smaller positions in ENA, UNI, PEPE and AAVE represented 7 to 15 percent of the reported holdings of each.
The USDC backing was above 108 percent, so that side looks intact. But the broader point is uncomfortable. "User funds are safe" means Binance will honour balances even though the assets behind some of them were stolen. It does not mean the reserves were untouched. The exchange is backstopping the gap from its own balance sheet, and the promise to do so is a company commitment, not a legal guarantee. Several lawyers quoted in the coverage said customers may need litigation to enforce it.
The next checkpoint is the 1 November proof-of-reserves snapshot. It can show whether Binance replenished the wallets. It cannot, by itself, prove that backing held continuously, because customer balances move and a top-up can mask a gap on the day of the snapshot.
What could be frozen, and what could not
About 2.7 to 3 billion dollars was frozen on-chain. Tether froze 1.567 billion USDT. Circle froze 800 to 825 million USDC. Ripple froze about 200 million dollars of XRP. World Liberty Financial froze 27 million USD1. The Arbitrum Security Council froze 8,426 ETH and 74.6 million ARB, worth about 30.5 million dollars.
The rest is harder. More than 2.4 billion dollars sits in assets that no issuer can freeze: about 420,000 ETH, 18,270 BTC and various tokens on other chains. CoinDesk reported that the attacker split the Bitcoin into 19 wallets, 17 of them holding roughly equal amounts, which makes recovery a matter of seizing keys rather than blocking a token.
The laundering has been fast and unusual. The attacker sold USDT to market makers and borrowed ETH against USDT on Aave, depositing 59.9 million USDT as collateral and borrowing 19,762 ETH, to get ahead of the stablecoin freezes. The loan remained open and near liquidation. Hundreds of millions of USDT were swapped into ETH through DEXs and market makers, with the attacker accepting up to a 26 percent loss against market price to move into assets nobody can freeze. One conversion turned 325 million dollars of stablecoins into 285 million dollars of ETH in about twenty minutes.
Chainalysis described an on-chain pattern it had not seen before: thousands of transactions in a short period, with funds repeatedly circulated among addresses and often sent back to earlier ones. That looks like automation-driven obfuscation rather than standard mixing. No mixer use had been observed in the first day, which is itself unusual; the Bybit case used bridges.
The attribution
Private firms attribute the theft with high confidence to TraderTraitor, the North Korean unit also tracked as Lazarus or APT38. The same group has been tied to Bybit, DMM Bitcoin, KelpDAO and a Bitget exploit. The evidence is on-chain and behavioural. Chainalysis saw Binance proceeds commingling in real time with funds from the Bitget exploit, including through THORChain, and ZachXBT confirmed the convergence at the same Ethereum address. The operational wallet was funded through Tornado Cash, the same pattern as Bybit and KelpDAO. The staging and pre-signed authorizations match prior operations.
That is an intelligence assessment, not a court finding. No arrests have been announced. Binance has not publicly named a group and says it is working with law enforcement to confirm identities. The caveat is real, but multiple independent firms converged on the same conclusion within a day.
What is still unresolved
The root cause is not public. Binance has promised a technical post-mortem, and until it lands, the initial vector remains a preliminary account from the company rather than a reconstruction from logs. Whether an insider was involved is also open; Binance says the investigation has not attributed responsibility to any individual and has referred to additional points of breach.
The legal position is open too. The attribution is private intelligence. The SAFU promise is a company policy. The reserve data shows a gap that the exchange says it will fill. Whether it fills it without customer impact depends on the recovery, the replenishment, and the 1 November snapshot.
Where this could be wrong
The biggest uncertainty is the attack chain. The EIP-7702 mechanics are well documented by TRM and Elliptic, but the path from a laptop to a signing system is Binance's preliminary account, not an independent forensic reconstruction. The company itself says the investigation is continuing.
The second uncertainty is the reserve arithmetic. CoinDesk's 94 percent figure is derived from the 1 October snapshot and the amount taken. Customer balances and hot-wallet balances move, so the exact backing ratio at any moment is not public.
The third is attribution. The on-chain links are strong, but "high confidence" is not proof, and no court has tested it.
The shape of the failure is clear. The attacker did not beat the cryptography. They got the signer to approve, and the feature that made the wallet programmable did the rest. That is the lesson exchanges should be writing down, and the reserve question is the one customers should be watching.
On this page
Sources
- North Korea Steals USD 6.36 Billion From Binance in the Largest Hack in HistoryTRM Labs, 2026
- Binance seeks to shore up confidence after record $6.3 billion heistReuters, 2026
- Binance hack drained wallets backing customer assets, reserve data showsCoinDesk, 2026
- Binance loses over $6 billion in biggest crypto hack in historyCoinDesk, 2026
- Binance hacker splits $1.4 billion of bitcoin into 19 wallets that no one can freezeCoinDesk, 2026
- TraderTraitor: North Korean State-Sponsored APT targets blockchain industryCISA, 2022
Frequently asked questions
Did the attacker steal Binance private keys?
Binance says it found no evidence of a private key leak. TRM Labs and Elliptic describe the compromise as one of the infrastructure and people around the wallets rather than the cryptography. The strongest evidence is that wallets on ten chains with different key types and signing schemes all produced valid signatures for the attacker inside the same short window, which is hard to explain with a single leaked key.
What is EIP-7702 and how was it abused?
EIP-7702, introduced in Ethereum's Pectra upgrade in May 2025, lets an ordinary externally owned account sign an authorization that makes it run a smart contract's code. The attacker prepared 50 signed authorizations that pointed at a sweeper contract and sent them in a batch. The hot wallet's nonce advances with every withdrawal, so one of the 50 eventually matched. The delegation then let the attacker move the wallet's balance to an address only they controlled.
Are customer funds safe?
Binance says it will honour balances and cover the loss from company funds and SAFU, and that it set aside about 6.34 billion dollars. CoinDesk's examination of Binance's reserve data says the emptied wallets were part of the assets backing customer balances, leaving ether backing near 94 percent until the exchange replenishes. The promise to cover is a company promise, and lawyers quoted in the coverage say it is not self-enforcing.
Who is behind the attack?
Private intelligence firms attribute it with high confidence to TraderTraitor, the North Korean unit also tracked as Lazarus or APT38, the same group the FBI tied to Bybit in 2025. The evidence is on-chain commingling with known DPRK proceeds, Tornado Cash funding of the operational wallet, and matching tradecraft. It is an intelligence assessment, not a court finding, and Binance itself has not publicly named a group.