Imagine a bank vault being emptied in less time than it takes to drink a cup of coffee. That is roughly what happened to Binance, the world's largest cryptocurrency exchange, on the evening of 29 October 2026.

Binance puts the loss at about $6.3 billion. Blockchain analysts estimate between $6.36 billion (TRM Labs) and $6.43 billion (Elliptic, as reported by SecurityWeek). Either way, it is the largest crypto theft on record: more than four times the $1.5 billion taken from Bybit in February 2025.

You do not need to own any cryptocurrency for this story to matter. The way the attack started, and the way part of the money was stopped, holds lessons for anyone whose accounts or devices can move money, data or systems. That includes most businesses, and plenty of households too.

The investigation is ongoing and Binance has promised a technical post-mortem. Facts below are as reported up to 3 November 2026.

First, three terms in plain English

  • Hot wallet. An exchange keeps most of its money locked away offline, but holds some "hot" (online) so customers can withdraw quickly. Think of it as the cash in a shop's till rather than the money in the safe.
  • Signing. Every crypto payment has to be approved, or "signed", digitally. Whoever controls the signing controls the money.
  • Stablecoin. A cryptocurrency pegged to a normal currency such as the US dollar. Unlike bitcoin, stablecoins can be frozen by the companies that issue them, which turned out to matter a great deal.

What happened, minute by minute

According to TRM Labs' on-chain analysis, this was no smash-and-grab. It was planned well in advance:

  • Preparation began at least 36 hours earlier. On 28 October an attacker's wallet was topped up with small amounts from Tornado Cash, a service used to hide where crypto comes from. On 29 October the attackers tested and rehearsed their code on other wallets before turning it on Binance.
  • At 20:05 UTC the theft began on the XRP Ledger, followed at around 20:20 UTC by Bitcoin, Tron and Ethereum. TRM says most of the money left Binance in about 20 minutes, with further sweeps until shortly before midnight.
  • Ten blockchains were hit (Elliptic counts eleven). TRM puts roughly $3.8 billion on Ethereum and about 18,270 bitcoin (around $1.5 billion) among the largest amounts.

On Ethereum, TRM describes an unusual trick. A Binance hot wallet signed 50 permission slips in advance, each handing control to a "sweeper" program run by the attacker, so that one of them would always be valid when needed. On the other blockchains the money left through ordinary approved transfers. TRM's assessment is that the attackers most likely took over Binance's hot-wallet signing systems: the machinery that approves money going out.

How did they get in?

Binance's first explanation was that the incident "may involve a compromised DevOps engineer's laptop", which gave the attacker access to part of its systems from which unauthorised withdrawals were sent (as quoted by CNBC). In other words, one engineer's computer appears to have been the front door. Binance said it had found no evidence that its secret wallet keys had leaked.

Days later, co-CEO Richard Teng said the investigation had "uncovered additional points of breach", that the attack "was not carried out by one person", and that the attacker used a self-destruct mechanism that wiped its tools and evidence (SecurityWeek, Reuters). He also said the Ethereum permissions "did not pass through our normal approval controls". Binance has not yet published the full root cause.

Who is behind it?

Within hours, TRM Labs and Chainalysis linked the attack to TraderTraitor, a North Korean state-sponsored hacking unit; TRM said it made the judgement "with high confidence". On 31 October the FBI said the same group was responsible. Working with the US Secret Service and IRS Criminal Investigation, it said the attackers were converting stolen assets "primarily into Ethereum" and expected further laundering through other crypto services.

The FBI published 628 cryptocurrency addresses (608 Ethereum, 19 Bitcoin and one Solana) and asked exchanges and analytics firms to refuse any transactions linked to them (SecurityWeek). It had previously blamed the same group for the 2025 Bybit theft.

The race to freeze the money

Here the story turns. Because much of the stolen money was in stablecoins, the companies behind them could freeze it, a little like a bank cancelling a stolen card:

  • TRM reports that Tether froze funds at 21:01 UTC and Circle at 21:04 UTC, less than an hour after the theft began, followed by Ripple, World Liberty Financial and the Arbitrum Security Council.
  • Estimates of the total frozen range from about $2.7 billion (TRM) to $2.85 billion (Elliptic); Binance put it at around $3 billion.
  • Bitcoin cannot be frozen this way, and analysts expect laundering of the rest to take months.

As TRM's Ari Redbord told CNBC, "A freeze stops the money from moving, and recovery follows through legal process."

Do Binance customers lose money?

Binance says no. It paused deposits and withdrawals, promised to cover all losses, and used its emergency customer fund (SAFU, the Secure Asset Fund for Users), part of its insurance fund and its own company money to buy back the missing assets. On 31 October it said it had replaced 90% of them; by 2 November SecurityWeek reported Teng's figure as about 95%. "Our users will not bear the financial impact of this incident," Teng said (Reuters). Withdrawals restarted in stages on 1 November.

Crypto prices fell, with CNBC reporting bitcoin below $78,000 on 30 October. But Sean Farrell of Fundstrat told CNBC the incident "does not currently appear to create meaningful solvency risk for Binance".

What it means for you

Take away the cryptocurrency and this is a familiar story: one trusted person's device became the way into the systems that move money. The same pattern sits behind many ransomware and invoice-fraud cases in UK organisations.

If you hold crypto or invest online: protect your exchange account with a passkey or an authenticator app, not just a password. Turn on withdrawal allow-lists if your exchange offers them, so money can only go to addresses you have approved. And be wary of anyone who contacts you offering to "recover" lost crypto for a fee.

If you run a small business: ask who can move money or change bank details, and from which devices. Make sure those accounts have MFA, and that any payment or bank-detail change needs a second person to confirm it, by phone, on a number you already know.

If you work in IT or at an MSP:

  1. Treat admin devices as crown jewels. Privileged work should happen on hardened, managed devices, separate from everyday email and browsing. In Microsoft 365, that means separate admin accounts, phishing-resistant MFA and device-compliance requirements for admin sign-in.
  2. Make approvals impossible to skip. Binance says the malicious permissions bypassed its normal approval controls. Payments, bank-detail changes, mass data exports and new admin roles should need a second person, and the control must not be skippable.
  3. Watch for unusual permissions, not just unusual logins. TRM recommends alerting on unexpected delegations or bulk signing requests. The equivalent elsewhere: alerts on new app consents, new mailbox forwarding rules and new privileged role assignments.
  4. Plan for evidence being destroyed. The attackers wiped their tools. Central, tamper-resistant logging, stored outside the systems an attacker can reach, is what makes an investigation possible.
  5. Rehearse the first hour. Billions were frozen because the right people acted within minutes. Know who you call (your MSP, your bank, Action Fraud and the NCSC) and practise it.
  6. Expect patient, well-funded attackers. State-backed groups prepare for days and test before they strike. The basics (least privilege, MFA, patching, monitoring) are what make that preparation fail.

The bottom line

The Binance theft broke records for its size, not its method. It began, as so many incidents do, with access that should have been better protected, and its damage was limited by people acting fast. Those are lessons anyone can apply this week, whether they look after a crypto exchange, a small firm or the family laptop.

This article summarises and comments on the reports listed below; figures and attribution may change as investigations continue. It is general information, not legal, financial or professional advice.