This analysis is based on Binance's initial findings and public on-chain research as of October 30, 2026. Binance has not yet published its technical post-mortem. We will update this breakdown when it does.
What happened
On October 29, 2026, an attacker moved funds out of Binance hot wallets on ten blockchains in a coordinated operation. According to TRM Labs, most of it left within about 20 minutes, starting at 20:05 UTC.
Binance estimates the total impact at around $6.3 billion. TRM Labs, valuing each transfer at the moment it was taken, puts it at about $6.36 billion. Early tallies published while the drain was still under way, including Blockaid's and CoinDesk's, put it at $5.5 billion or more. On any of these figures it is the largest crypto theft on record, roughly four times the $1.5 billion Bybit hack of February 2025.
Binance says user funds are safe and that it will cover all losses from the SAFU fund and company funds. Deposits are operating normally. Withdrawals remain paused while Binance rebuilds the withdrawal service and its related addresses, and the exchange said on October 30 that it expects to resume them within 48 hours.
Binance's initial finding
Binance says its initial investigation suggests the incident may involve a compromised DevOps engineer's laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. It says it has found no evidence of any wallet private key leak. In a later update it described the incident as stemming from multiple factors, with the compromised computer as the possible entry point.
On the morning of October 30, Binance went further. It said follow-up investigation has uncovered additional points of breach beyond the laptop, called the incident a complex attack, and said it is coordinating with partners. It has not yet said what those additional points are. The laptop should therefore be read as one likely foothold, not the full explanation.
That distinction matters. If the keys never left their secure environment, the attacker did not need them. Access to a system that could ask the keys to sign was enough.
Preparation
TRM Labs traced the preparation back at least 36 hours. On the morning of October 28, an attacker operator wallet received three small withdrawals from Tornado Cash. Early on October 29, it deployed a first version of its sweeper code and tested it on two wallets. Later that day it rehearsed a final version on a third wallet and routed the test funds back to itself. About four hours after that rehearsal, the same code was installed on a Binance hot wallet.
The opening move on XRP
The first theft came on the XRP Ledger. Between 20:05 and 20:09 UTC, five Binance wallets sent 233.46 million XRP, about $296 million, to a single attacker address, according to TRM Labs. On Bitcoin, Tron, Solana and the other non-Ethereum chains, funds left through ordinary signed transfers. TRM Labs reads this as a compromise of Binance's hot wallet signing infrastructure.
The Ethereum step: 50 signatures, one nonce
On Ethereum, the attacker did something different. At 20:20:59 UTC, an operator address funded through Tornado Cash sent an EIP-7702 set-code transaction, type 0x04, to Binance 14, one of the exchange's busiest Ethereum hot wallets. It carried no value and no calldata. Its payload was an authorization list of 50 entries. Each was signed with the Binance 14 key, and each delegated the wallet's code to a sweeper contract the attacker had deployed that day.
An EIP-7702 authorization is a signature over three values: the chain ID, the address of the contract to delegate to, and a nonce. It only takes effect if that nonce equals the account's current nonce at the moment the transaction executes. Binance 14 was paying out withdrawals continuously. According to on-chain analysis by 808bits, it sent 33 transactions in the three minutes before the attack, about one every six seconds. Any single nonce the attacker picked would probably be stale before it landed.
The answer was to sign a window. The 50 authorizations covered nonces 18,914,775 to 18,914,824. When the transaction executed, the wallet's live nonce was 18,914,809. That entry applied, and the protocol simply skipped the other 49. From that moment, any call to Binance 14 ran the attacker's code, while Binance's own withdrawals kept flowing from the same address.
Three minutes and 24 seconds later, a single call to the delegated wallet swept about 167,464 ETH and 63 tokens, including 1.615 billion USDT, to an address that had never received funds. Researchers valued that one transaction at roughly $2.5 billion to $2.8 billion. Within 12 minutes of that sweep, Blockaid reports, 10 more Binance hot wallets on four chains sent funds to the same address.
Why it slipped past controls
Researchers who analysed the transaction point to a detail the post-mortem will need to address. An EIP-7702 authorization has no recipient, no amount and no calldata. A signing service that receives a 32-byte digest cannot tell it apart from a transaction hash, and a policy engine that checks destinations and limits has nothing to check.
The 50-nonce window also suggests the attacker could not control exactly when the signatures came back. That fits access to a signing path rather than possession of a raw key. With the key itself, a direct transfer would have been simpler. This is researchers' analysis, not a confirmed finding. Binance has not said how the signatures were obtained.
The delegation was also persistent. Under EIP-7702, delegated code stays attached until the account signs a new authorization that replaces it or clears it to the zero address. Blockaid and other researchers report that the attacker used the still-delegated wallet to reach a separate Binance smart-contract wallet that recognised Binance 14 as an operator, moving several hundred million dollars in USDC. Reported figures range from about $780 million to $823 million. Researchers also report that deposits Binance's systems kept routing into Binance 14 were swept again later that evening. Binance says it has since revoked the affected address authorisation.
Freezes
Issuers and networks moved quickly. Tether froze more than 1.567 billion USDT. Circle froze more than $800 million in USDC. Binance co-founder Yi He said Ripple froze about $200 million, and Ripple said it was actively freezing RLUSD linked to the attack. Yi He also said World Liberty Financial froze about $27 million in stablecoins and about $2 million in WLFI tokens. Arbitrum's Security Council used an emergency action to move 8,425 ETH and about 74.56 million ARB, roughly $30.5 million, from an attacker address into a frozen wallet that can only be released by further Security Council action or an ArbitrumDAO vote.
Binance puts the verified frozen total at around $3 billion. TRM Labs estimates about $2.7 billion and says the attacker raced the freezes by selling USDT to market makers and borrowing ETH against USDT on Aave. By TRM's count, the attacker now holds more than 420,000 ETH and 18,270 BTC beyond any issuer's reach. Frozen is not the same as recovered.
Attribution
Binance has not named an attacker. TRM Labs attributes the attack, with high confidence, to TraderTraitor, a North Korean unit linked to the Lazarus Group. Chainalysis CEO Jony Levin said the firm assessed it was likely TraderTraitor. ZachXBT reported that funds from the Binance exploit and the $388 million Bitget exploit were commingled at the same address after arriving through THORChain, which indicates the same actor is likely behind both. The Bitget exploit had earlier been attributed to TraderTraitor. CNN reports that North Korea is suspected.
What is still unknown
What the additional points of breach are, and how the attacker got from an engineer's laptop to a service container that could request signatures.
Whether authorization digests went through the same policy checks as withdrawals, or around them.
Why hot wallets on several chains signed outbound transfers in the same window.
How much of the frozen value will ultimately be returned to Binance.
Binance has promised a detailed technical post-mortem and an updated Proof of Reserves. We will revise this analysis when they are published.
Defenses
This attack chain maps to three layers of defense. The first is signer policy that understands EIP-7702, recognising type 0x04 transactions and 0x05-prefixed authorization digests and refusing to sign delegations for hot wallets by default. The second is endpoint hardening for engineers whose machines can reach production. The third is segregating the withdrawal service, so that one compromised container cannot request arbitrary signatures.
The concrete controls, detection rules and a review checklist for each layer are covered in the Advanced Security Academy. Academy waitlist coming soon.
Sources: Binance statements on X (October 29 and 30, 2026); TRM Labs; Blockaid; 808bits; drk.vc; Chainalysis via CoinDesk; CoinDesk; CNBC; Reuters; CNN; Arbitrum Foundation governance forum; ZachXBT; Tether CEO Paolo Ardoino; Circle CEO Jeremy Allaire; Ripple; EIP-7702 specification.