No key was stolen. $6.3 billion still left.

This one is not a server falling over. On 29 October, about $6.3 billion left Binance's hot wallets in minutes. For about two days, its users could not take their money out.

Binance has not published its full report yet. This is what we know today, from Binance's own updates and from the teams tracing the money. We'll update it when the real report lands.

Read the whole story ↓
Who
Binance, hot wallets and withdrawals
Outage on
29 Oct 2026
Down for
~2 days
Source
Binance: Security Incident Update (30 Oct 2026)

Also: Binance, Recovery Update #4, withdrawals resume in phases (1 Nov 2026), and The Hacker News' summary of the outside analysis.

What happened

On 29 October, around 20:05 to 20:20 UTC, the main wave of withdrawals left Binance's hot wallets. Per Binance, a compromised laptop gave the attacker a way into a service container. From there, the attacker submitted withdrawals the system treated as real. Binance says no wallet private key was leaked.

Binance's co-CEO says it was not one person's access and "not a single 'one-click' action". Binance later found "additional points of breach". Outside analysts (TRM Labs, Elliptic) say the attacker got Binance's own signing system to approve transactions in advance, including one batch of 50, then emptied a wallet in about 3 minutes. Binance has not confirmed this.

Binance removed the attacker's access the same night and suspended withdrawals. Deposits kept working. About $3 billion was frozen on-chain by stablecoin issuers and others.

On 1 November at 06:00 UTC, withdrawals began to come back in phases, Bitcoin first, then 15 networks. Binance says it has covered about 95% of the losses from its own funds, and that users will not lose money.

The WTF

Everyone guards the private keys. Here, by every account so far, the keys stayed safe. The weak point was the system allowed to use them. If a system can sign, then whoever can talk to that system can sign too. And the outage came after the theft. Turning withdrawals back on safely took longer than the theft itself: about 20 minutes to take the money, about two days to let people move theirs again.

Bingo 0 of 9. A rare one. Nobody saw this coming. Make your team's card →

The lesson

Guard the service, the container and the path to it, not only the secret.

Laptops are part of production when they can reach production.

Plan the way back. A stop button is fast. Turning things back on, asset by asset with checks, is the slow part, so practise it.

The thing that can sign is as valuable as the key.

#HugOps

To the Binance teams who stopped it the same night and have been bringing withdrawals back one network at a time. And to the stablecoin and security teams around the world who froze billions on-chain.

Pass the card on

Download the card