Binance Hack: $6.3 Billion Stolen in 20 Minutes. Here Is What Happened, Who Did It, and Where the Money Is Now. — Sovereign Discovery
S|D
Sovereign DiscoveryeDiscovery & Litigation Support
Short on time? Listen to this article below.
Newsletter · Issue 27

Binance Hack: $6.3 Billion Stolen in 20 Minutes. Here Is What Happened, Who Did It, and Where the Money Is Now.

On October 29, hackers drained Binance, the world’s biggest crypto exchange. It is the largest crypto theft on record. This is the full story in one place: what happened, how, who did it, what has been recovered, and what every company should take from it.

On the evening of October 29, 2026, about $6.3 billion in crypto left Binance’s wallets in a few minutes. It is the biggest crypto theft on record, about four times bigger than the Bybit hack of February 2025.

Binance says customers will not pay for it. The company is covering the loss with its own money. The FBI says North Korea did it. Some of the stolen money is frozen. A lot of it is not.

Here is everything we know as of November 2, in plain language.

$6.36B
stolen, according to blockchain firm TRM Labs
20 min
for most of the money to leave, across ten blockchains
~$2.7B
frozen by stablecoin issuers and Arbitrum (TRM count, Oct 30)
95%
of affected assets Binance says it has replaced with its own money
The Short Version

Six Facts in 60 Seconds

What: About $6.3 billion stolen from Binance’s online wallets on October 29, most of it in 20 minutes.

Who: North Korea’s hacking group TraderTraitor, says the FBI.

How: Binance first pointed to a hacked engineer’s laptop, then found more break-in points. TRM believes the attackers took over the system that approves Binance’s transfers. There is no full report yet.

Frozen: About $2.7 to $3 billion, by Tether, Circle, Ripple, World Liberty Financial, and Arbitrum.

Still loose: About $2.4 billion was in the attacker’s hands on October 30, and it is moving.

Customers: Binance says it has replaced about 95% of affected assets and users will not pay for the loss. Withdrawals reopened in phases on November 1.

Visual Overview
From Preparation to Reopening — Five Key Moments
1 Oct 28 — The attacker funds a wallet with small Tornado Cash withdrawals Preparation starts at least 36 hours before the theft (TRM Labs). 2 Oct 29, 8:05 p.m. UTC — Money starts leaving Binance on ten blockchains Most of the $6.36 billion is gone in about 20 minutes. 3 Oct 29, night — Issuers freeze funds. Binance pauses withdrawals. Tether, Circle, Ripple, World Liberty and Arbitrum freeze about $2.7 billion. 4 Oct 30–31 — TRM, Chainalysis, then the FBI name North Korea’s TraderTraitor Binance sets aside $6.34 billion and says 90% of affected assets are replaced. Nov 1–2 — Withdrawals reopen in phases. Binance says 95% is replaced. $4.65 billion left in the first 9.5 hours. Fiat withdrawals return Nov 2.
01

The Attack: 20 Minutes, Ten Blockchains

The hackers took control of Binance’s hot wallets. A hot wallet is the online wallet an exchange uses to pay customer withdrawals. Binance says most customer money sits offline in cold wallets and moves to a hot wallet only when someone withdraws. The attackers went after the online part.

The theft started at 8:05 p.m. UTC on October 29. In about 20 minutes, Binance wallets on ten blockchains sent their money to addresses the attacker controlled. A smaller second wave followed around 11 p.m. UTC. The biggest loss was on Ethereum (about $3.8 billion), then Bitcoin (18,270 BTC, about $1.5 billion) and Tron (about $628 million).

It was planned. TRM Labs says preparation began at least 36 hours before the theft. The attacker funded a wallet with small amounts from Tornado Cash, a service that hides where crypto comes from, then tested and rehearsed the attack code.

How did they get in? Binance first said a hacked laptop belonging to a DevOps engineer may have given the attackers access to a company system. Later it said investigators found more break-in points. Its co-CEO says it was not one person, and that the attackers used a self-destruct feature that makes the investigation harder. TRM’s view is that the attackers got control of the system that approves Binance’s transactions, and used it on many chains at once.

Most of the $6.3 billion left in 20 minutes. The planning took more than a day.

02

North Korea, According to the FBI

On October 31, the FBI said North Korea was responsible. It named the group TraderTraitor, the same group it blamed for the $1.5 billion Bybit hack in February 2025.

TRM Labs and Chainalysis named the same group within a day. TRM says the attack matches earlier North Korean thefts: small Tornado Cash withdrawals to fund the attacker’s wallet, setup long before the theft, and approvals prepared in advance and used all at once.

The FBI worked with the Secret Service and IRS Criminal Investigation. It published 628 addresses linked to the theft (608 Ethereum, 19 Bitcoin, 1 Solana) and asked crypto businesses to block them. Experts say North Korea steals crypto to help fund its weapons programs.

03

Frozen Is Not the Same as Recovered

Stablecoin companies moved fast. A stablecoin is a token tied to the dollar, and its issuer can freeze it. Tether froze about $1.77 billion. Circle froze about $825 million. Ripple froze $40.5 million, World Liberty Financial $27.8 million, and Arbitrum’s emergency council about $30 million. TRM counts about $2.7 billion in total as of October 30, and Binance puts it near $3 billion. The numbers keep rising as more is frozen.

But frozen means stuck, not returned. The rest is on the move. TRM counted about $2.4 billion in the attacker’s hands on October 30, mostly Ether and Bitcoin that no company can freeze. Chainalysis says the hackers moved more than $500 million through Tron, using over 1,000 addresses, then out through swap services to new wallets on Ethereum, Bitcoin, and Solana. The FBI expects more laundering.

For customers, Binance set aside about $6.34 billion of its own money. It says it has replaced about 95% of the affected assets, using its treasury, an insurance fund, and its SAFU emergency fund. Binance says main coins like BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC are fully backed, and that the last 5% is smaller tokens that take longer to buy.

Withdrawals were paused, then reopened in phases starting November 1. In the first 9.5 hours, $4.65 billion went out and $1.01 billion came in. Binance says the net outflow was 2.1% of its assets and is stabilizing. Fiat withdrawals returned on November 2.

Section 3 · Visual
Who Froze What — About $2.7 Billion, Not Yet Returned
Tether $1.77B Circle $825M Ripple $40.5M World Liberty $27.8M Arbitrum council ~$30M Source: TRM Labs, October 30, 2026. Later reports show Circle alone above $1.1 billion.
04

What Customers and Companies Should Take From This

If you use Binance, know that scammers are active. Fake posts claim Binance is paying a $150 “compensation reward.” Binance says they are fake. Use only official channels, and remember that Binance’s proof-of-reserves page shows its backing.

If you run a company, this is also an evidence case. A loss this size draws investigators, regulators, partners, and customer lawyers. Whatever they ask for will come from the records you keep today: access logs, device images, messages, and vendor records. Binance’s own early statement, that a laptop may have been the way in, was later widened by its investigators. Public statements get compared with the internal record, so keep a dated record of what was known and when.

Section 4 · Visual
The Incident Records Checklist — Four Steps That Protect You Later
1 Freeze your own logs now Signing system, admin access, cloud, VPN, and endpoint logs. Stop auto-delete and log rotation. 2 Image the devices involved before anyone cleans them A compromised laptop or server is evidence. Keep a chain-of-custody record. 3 Issue a legal hold that reaches vendors and partners Cloud providers, token issuers, security firms, and exchanges all hold records about the event. Match every public statement to the internal record Keep a dated log of what was known and when, so your story stays consistent.

Five Things to Remember From the Binance Hack

  • Online wallets are the weak spot. Money that is online can be stolen online. Binance says most customer money sits in cold wallets, and the hot-wallet theft was still $6.3 billion.
  • One approval can be too much power. One security expert said it looked like a single approval gave the attacker lasting access. Approvals should expire and need a second check.
  • Preparation leaves a trail. The attacker spent at least 36 hours getting ready. Good logging can catch the setup, not just the theft.
  • Speed saves money. Freezes in the first hours stopped about $2.7 billion from moving. Companies that already know who to call at issuers and exchanges act faster.
  • Frozen is not recovered, and scams follow every headline. Watch the official updates, and treat any message offering compensation as fake until Binance confirms it.
Industry Perspective — Sovereign Discovery

A hack this size is a technical story first and an evidence story second. As soon as the money moves, the records start to matter: logs, device images, messages, vendor contracts, and public statements.

At Sovereign Discovery, we help companies keep those records safe and usable before anything goes wrong, so that when investigators, regulators, or lawyers ask, the answer is ready within hours, not weeks.

Final Thought

Hackers took $6.3 billion in 20 minutes. They prepared for more than a day, and the rest of the world needed days to respond. Binance says customers will be made whole and the FBI says North Korea is behind it. Billions are frozen, and billions are still moving. The case is not over.

For any company, the lesson is the same: the records you keep before the day something goes wrong decide how well you can respond after.

Figures come from TRM Labs, Chainalysis, the FBI, Binance, Reuters, AP, and other news reports as of November 2, 2026, and may change as the investigation continues. This newsletter is not financial advice.

Could your company produce its security records within 24 hours of an incident?
Schedule a Consultation