The Binance Hack: Who Absorbed the Largest Theft on Record
About $6.4 billion was taken from Binance on 29 October, most of it within 20 minutes. Stablecoin issuers froze 44% of it, Binance replaced most of the rest from its own reserves, and no insurance policy was large enough to help. For institutional investors, the lesson is about who stands between them and the blockchain.
Photo: 東京のエビフライ at Japanese Wikipedia, CC BY-SA 3.0 via Wikimedia Commons
By Fabian Fach, Founder, Black Flower Capital
On 29 October, attackers took about $6.4 billion in cryptoassets from Binance, the exchange that handles roughly 40% of spot trading among the ten largest venues, according to CoinGecko and Kaiko. Estimates of the loss range from about $6.3 billion (Binance) to $6.36 billion (TRM Labs) and $6.43 billion (Elliptic), depending on when each asset is priced. Most of it left within about 20 minutes of the first transfer at 20:05 UTC, across at least ten blockchains. Elliptic describes it as the largest theft of any kind on record, more than four times the $1.46 billion taken from Bybit in February 2025. On 31 October the FBI attributed the theft to TraderTraitor, a North Korean hacking group. North Korea denies involvement.
For investors, what happened in the following 72 hours matters more than the theft itself. A system designed to work without trusted intermediaries was rescued by a small number of them, and insurance played no visible part.
How the Binance Hack Worked
No blockchain was broken. Every transfer was valid on the chain it ran on. What failed was Binance's control over who could authorise those transfers.
According to Binance's preliminary findings, published on 3 November and reported by the New York Times and SecurityOnline, the intrusion began months earlier: a tampered software installer on one wallet engineer's computer in June, then a fake recruiter who got a second engineer to download a malicious "assignment" in September. From there the attackers abused an internal AI tool to reach further engineers and, in the end, an internal signing service. On Ethereum they used EIP-7702, a feature that lets an ordinary wallet delegate execution to code, to give a contract they controlled authority over a Binance hot wallet. Binance said these on-chain permissions "operated independently of Binance's normal withdrawal infrastructure". It has not explained in detail how the AI tool was misused.
Because the delegation sat on the blockchain itself, suspending withdrawals did not stop it. Binance removed the attackers' access at 00:10 UTC on 30 October, about four hours after the first transfer. In October we wrote about AI agents acting outside their overseers' view. Here an internal AI tool was one of the steps between a compromised laptop and control over billions.
The Rescue Came From Central Actors
Within about an hour, Tether and Circle, the issuers of the two largest dollar stablecoins, began freezing stolen tokens. Reuters counted $2.38 billion frozen by the two that night. TRM Labs put issuer freezes at about $2.67 billion by 00:30 UTC on 30 October, including smaller amounts frozen by Ripple and World Liberty Financial, and the Arbitrum Security Council froze about $30 million at the network level. Circle froze all 823 million stolen USDC before any of it could be swapped. By 7 November, Elliptic counted $2.85 billion frozen or seized, 44% of the total.
Binance then replaced most of what was lost. It said it had replenished 90% of the stolen assets by 31 October and 95% by 1 November. Reuters reported that the money came from about half of its Secure Asset Fund for Users, a bitcoin reserve of about $1 billion, and from parts of its futures insurance fund and corporate treasury. Withdrawals reopened on 1 November. Customers took out a net $3.6 billion, about 2% of assets, in the first hours, according to Reuters and CNBC. Higher outflow figures from DefiLlama were disputed by Binance because they left out transfers to a new hot wallet.
The rescue depended on concentration. Tether's USDT and Circle's USDC together account for about 84% of the roughly $295 billion of dollar stablecoins in circulation, according to DefiLlama and CoinGecko. That is why two companies could stop more than $2 billion moving within an hour. The same power applies to every holder of those tokens, not only to thieves. The attackers were the participants who acted most like decentralisation purists: Elliptic estimates they converted about $786 million of stablecoins into other assets before the freezes landed, and the 18,270 stolen bitcoin, which no issuer can freeze, had not moved by 7 November.
The Insurance Gap
The loss exceeds the capacity of any available crypto insurance policy, Marcos Alvarez of Morningstar DBRS told Reuters on 6 November. Size is only part of the gap. Since 31 March 2023, Lloyd's has required standalone cyber policies written in its market to exclude state-backed cyber attacks, under Market Bulletin Y5381. With the FBI attributing this theft to North Korea, Alvarez said insurers "may dispute or deny claims" in such cases, and the exclusions have not been tested on a loss like this.
Brokers expect closer questions at renewal rather than a market retreat. Marsh's Jacqueline Quintal said she did not anticipate material changes in capacity, pricing or coverage. For now, a loss of this size sits on the victim's balance sheet. Binance could absorb it. A smaller exchange, custodian or fund administrator might not.
How Markets Priced the Binance Hack
Bitcoin fell 5.0% and ether 4.2% in the 24 hours from 20:00 UTC on 29 October, based on Yahoo Finance hourly prices. Sky News and the New York Times also reported a fall of about 5% for bitcoin. Listed intermediaries fell further. Coinbase shares lost 10.6% on 30 October and Circle 9.3%. Coinbase also reported quarterly results that week, so not all of its fall is due to the hack.
Shares in the firms that stand between investors and the blockchain fell about twice as far as bitcoin. The market priced the hack as a business risk for those firms more than as a threat to the assets themselves.
Questions Allocators Should Ask Their Counterparties
For family offices, pension funds and CIOs with crypto exposure, direct or through a fund, the hack turns into a short list of questions for every exchange, custodian and stablecoin they rely on:
- What share of assets sits in hot wallets, and are client assets segregated from the venue's own?
- Who, and what, can authorise a transfer? Do delegation features such as EIP-7702 go through the same approval controls as withdrawals, and can internal tools, including AI tools, reach the signing system?
- What does the insurance actually cover? Is there a state-backed or war exclusion, and how is attribution decided?
- Who pays if reserves are not enough? Binance's reserve fund and treasury were large enough this time, and it said it set aside about $6.3 billion of company funds. Ask what the equivalent is at each counterparty.
- How exposed are you to an issuer's freeze power? It protected Binance's users here, and it is also a form of counterparty risk.
What to Watch
- Laundering of the remaining funds. Elliptic counts about $3.13 billion still in addresses linked to the theft, including the 18,270 unmoved bitcoin.
- Reopening of the remaining Binance withdrawals, and whether outflows pick up again.
- Insurance renewals. Reuters reports that underwriters are re-examining their crypto books.
- Attribution. The FBI's attribution affects how the insurance exclusions apply. Elliptic and TRM Labs reached the same conclusion, and North Korea rejects it.
This article describes a reported event and is not investment advice. Figures are as published by the named sources between 29 October and 7 November 2026, and estimates of the stolen total differ by source.