mythsthe peopleBinance2026crypto exchange / global

everyone assumed:

the money is safe as long as the keys never leave

what was actually true:

Whatever is allowed to ask for a withdrawal can empty the wallet, wherever the key happens to be.

how it happened

  1. whoattackerstaging from 28 October
  2. the gapDevOps laptopreached a service container
  3. thenhot walletsten blockchains, about 20 minutes
  4. the resultabout $6.3Babout $3B frozen by partners
the gap that let it happen the result

what everyone assumed

Crypto custody has spent a decade on one idea: protect the private key. Hardware security modules, multi-party signing, cold storage, key ceremonies. The reasoning is sound as far as it goes. A transaction on a blockchain is only valid with a signature, the signature needs the key, and a key that never leaves its vault cannot be copied. Exchanges offer this as reassurance and customers repeat it, because it is true. If the keys are safe, the money is safe.

what happened

On 28 October 2026, according to TRM Labs’ on-chain analysis, a wallet controlled by the attacker received three small withdrawals from Tornado Cash, a mixing service. On the morning of 29 October the same operator tested attack code on two wallets of its own, then rehearsed the final version on a third. About four hours after the rehearsal, TRM found the code on a Binance hot wallet.

At 20:05 UTC on 29 October, TRM’s timeline shows five Binance wallets on the XRP Ledger sending 233.46 million XRP to a single address. Solana and Optimism followed. At 20:20 the Bitcoin hot wallet sent 18,270 BTC, and one Ethereum transaction carried 50 authorisations signed in advance. About three minutes later the Ethereum hot wallet sent its entire balance in one transaction. TRM counts about $6.36 billion leaving Binance across ten blockchains, most of it in roughly 20 minutes, with a second wave on Avalanche and Polygon at 23:05.

On 30 October Binance’s co-CEO Richard Teng gave the first account of the cause. The initial investigation pointed to a compromised laptop belonging to a DevOps engineer. The laptop gave the attacker access to a service container, and from that container the attacker submitted unauthorised withdrawal transactions. Binance said it had found no evidence that any wallet private key leaked.

Later the same day the account widened. Binance said the investigation had found additional points of breach, and Teng said the attacker had not simply used one engineer’s permissions and that the theft was not a single one-click action. Binance has not said how the laptop was compromised or what the other points of breach were.

TRM Labs attributes the theft to TraderTraitor, a North Korean state group, and says it makes that judgement with high confidence. Chainalysis calls TraderTraitor the likely culprit. Binance has not attributed the attack, and these are assessments by analytics firms. The same group was named by the FBI for the Bybit theft in February 2025, which started on another company’s developer laptop.

step by step

  1. the keys stay in the vaultWithdrawals are requested by internal services, and the wallets sign what those services ask for.
  2. 28 October 2026the attacker stagesTRM Labs traces small Tornado Cash withdrawals into an operator wallet and test runs the next morning.
  3. 29 October 2026, 20:05 UTCunauthorised withdrawals go outFrom a service container the attacker reached through a DevOps engineer's laptop, according to Binance.the assumption breaks here
  4. ten blockchains in about 20 minutesTRM Labs counts about $6.36 billion leaving Binance wallets.
  5. 30 October 2026Binance names the laptop, then moreAdditional points of breach found; no evidence of a private key leak; a post-mortem promised.

how it surfaced

The money moved on public ledgers, so the theft was visible as it happened. The blockchain security firm Blockaid flagged billions in outflows from Binance hot wallets, Binance confirmed a security incident, and withdrawals were suspended.

Stablecoin issuers can freeze their own tokens wherever they sit, and they did. TRM’s timeline has Tether freezing 971.1 million USDT at 21:01 UTC, 56 minutes after the first outflow, and Circle freezing 823 million USDC at 21:04. Binance said partners froze about $3 billion in total; TRM’s own count at 00:30 UTC on 30 October was about $2.7 billion. TRM also traced the attacker selling stolen USDT to market makers at a discount of more than 10% to turn it into ether before it could be frozen.

Binance put the loss at about $6.3 billion and, according to The Block, set aside $6.34 billion of its own funds and reserves to cover it. TechCrunch reported it as the largest known theft of cryptocurrency. The previous record, Bybit, was about $1.5 billion according to the FBI. Binance has promised a full post-mortem and an updated proof of reserves. As of 30 October 2026 neither has been published, so the laptop is the entry point Binance named on the first day, and the rest of the chain is still open.

Whatever is allowed to ask for a signature can spend the money.

The key can stay in its vault and still sign for the attacker, if the attacker controls something the vault is built to obey. Every service that can request a withdrawal, and every laptop that can reach that service, sits inside the same perimeter as the key.

picture it at a company like yours

The company here is made up. The other two paths are not: they happened, and each links to the story.

your company
a normal dayYour company pays suppliers through a banking portal, and a script on a server prepares the payment batches.
the gap nobody seesOne engineer's laptop can reach that server, because that is where they fix things when the script breaks.an outside tool that can do anything
  1. in this story
    the day it mattersSomeone takes over the laptop and asks the script for a batch nobody ordered.
    what it costs youThe bank sees a normal request from the usual place, and the money goes.
  2. or it goes like this
    howYour IT provider's remote-management tool is broken into.
    what leavesevery computer it manageswho ends up with ita ransomware crew hitting all its clients at once
    it happenedKaseya VSA, 2021
  3. or it goes like this
    howThe master key of a remote-support product is stolen.
    what leavesstaff computers and the documents on themwho ends up with ita state-sponsored group
    it happenedUS Treasury and BeyondTrust, 2024

sources

  1. Binance on X: initial investigation suggests a compromised DevOps engineer's laptop (30 October 2026)
  2. TRM Labs: North Korea steals USD 6.36 billion from Binance in the largest hack in history
  3. TechCrunch: North Korean hackers blamed for stealing record $6.3B in Binance breach
  4. The Block: Binance says it has $6.34 billion ready to cover hack losses
  5. Disruption Banking: Binance says DevOps laptop may have been the entry point in $6.3bn incident
  6. Dexerto: Binance responds to $6 billion crypto hack after claims a single laptop was to blame
  7. FBI IC3: North Korea responsible for $1.5 billion Bybit hack (I-022625-PSA)

← all myths

your turn

what you can do about it

  1. this week

    List every machine and account that can ask your payment or release systems to act.

    Most companies have a short list of systems that move money or change production: the banking portal, the payroll run, the deploy pipeline, the admin console of the main business app. For each one, write down what can trigger it (people, laptops, service accounts, tokens) and whether a single request can move everything at once. Binance kept the keys in the vault; the open question in its investigation is what was allowed to ask the vault for a signature.

  2. go deeper

  3. if you're not sure where to start

    Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.

    open the checklist →

the letter · every two weeks

one access gap in your inbox, with the fix.

Every issue takes one way access creeps in, shows a real incident where it went wrong, and ends with one thing to check that week. Written for the people who run the tools, without a security team behind them.

  • 1one mechanism, explained plainly
  • 2one real incident, taken apart
  • 3one step you can take on Monday

get the next issue

One email every two weeks. Your address stays here and is never passed to vendors. One click to unsubscribe. Privacy.