packet-autopsy.com

Case 012 · Incident: 29 Oct 2026

Binance hack: the record crypto heist had a test run first

On October 29, 2026, an attacker drained Binance hot wallets across ten or more blockchains, moving roughly $6.3–6.4 billion, most of it within about 20 minutes starting at 20:05 UTC. It is the largest crypto theft on record. Binance's initial investigation pointed to a compromised DevOps engineer's laptop that gave access to a service container used to submit unauthorized withdrawals.

Watch on YouTube

Twenty Minutes

On Thursday evening, October 29, 2026, hackers stole $6.3 billion from Binance, the world's largest crypto platform, the exchange says. It is likely the largest crypto theft in history.[1] Most of it moved in about 20 minutes from 20:05 UTC, across ten or more blockchains.[2][3] Reports say the first public alarm came from an independent researcher on X, not from Binance. Binance's first word was that user funds were completely safe.[4][5]

Binance first blamed one engineer's compromised laptop. Then it said it had found additional points of breach, and it has not said what they are.[6][7] Stranger still: the theft was rehearsed on the blockchain hours earlier, and one wallet kept being emptied long after the first blow. We will get to both.[2]

The Signals Before 20:05

TRM Labs, a blockchain analytics firm, found that preparation began at least 36 hours before the theft. Starting the morning of October 28, the attacker's operator wallet received three small withdrawals from Tornado Cash, a service that hides where crypto comes from.[2] On October 29, the operator tested its attack code on two wallets, then rehearsed the final version on a third and routed the test funds back to itself.[2] TRM says the same code was installed on a Binance hot wallet four hours after that rehearsal. A hot wallet is an online wallet an exchange keeps ready to pay out withdrawals. On Ethereum, that hot wallet was pointed at the attacker's code at 20:20 UTC, after the theft on the XRP Ledger had already begun.[2]

Binance has not said whether its own systems noticed any of this preparation.[2]

The Drain

At 20:05, the first blow landed on the XRP Ledger. In four minutes, five Binance wallets sent 233.46 million XRP to one attacker address.[2] At 20:20, a Bitcoin hot wallet sent 18,270 bitcoin to an attacker address, which began splitting it into round pieces. Within two minutes, a Tron hot wallet sent 612.7 million USDT, Tether's dollar token, plus 46.4 million TRX.[2] On Ethereum, also at 20:20, the operator submitted one transaction carrying 50 authorizations, each signed by the Binance hot wallet.[2]

They used a feature called EIP-7702, which lets an ordinary wallet delegate itself to contract code. Each pointed to a sweeper contract that obeys only the operator.[2] Three minutes and 24 seconds later, one transaction moved the wallet's entire balance: 167,464 ether and 63 tokens, including 1.615 billion USDT.[2] That wallet was also the executor of a separate Binance smart account. The role let the attacker pull another 823 million USDC.[2]

TRM puts the Ethereum losses alone at about $3.79 billion.[2] The drain hit ten blockchains by TRM's count, 11 by Elliptic's. TRM's assessment is that the attacker most likely gained the ability to make Binance's hot wallet signing system sign transactions of its choosing, across chains.[2][3] That fits Binance's own finding: no evidence that any wallet private key, the secret that controls a wallet, had leaked.[6]

What the Defenders Saw

Nothing public shows what Binance's own monitoring caught, or when. What the record does show is how fast the token issuers moved.[2][4][5] Stablecoin issuers can freeze their own dollar tokens. At 21:01 UTC, Tether froze 971.1 million USDT in the main receiving wallet. That was 37 minutes after the main sweep.[2] Three minutes after Tether's freeze, Circle froze 823 million USDC, in coordination with law enforcement. Ripple, World Liberty Financial and First Digital froze their tokens too.[2][8]

But one door stayed open. The attacker's delegation on that Ethereum hot wallet stayed in place.[2] As new funds reached the wallet, the attacker swept them again: at 20:41, 20:59, 21:04, 21:44, 22:39, and finally 23:56 UTC.[2] Around 23:05, a second wave hit Binance wallets on Avalanche and Polygon.[2]

Binance suspended deposits and withdrawals and revoked the affected address authorization. When exactly that revocation happened is not public.[6] At 00:08 the next day, the Arbitrum network's Security Council used emergency powers to pull about $30 million out of the attacker's wallet.[2] Elliptic, another analytics firm, notes the attacker held most of its USDT for 37 minutes on Ethereum and 46 on Tron. Our read: that pause gave the issuers their window.[2][3]

How much is frozen depends on who counts. Binance says $3 billion verified. Elliptic verified $2.84 billion, 44% of the theft.[3][8] Some of the loot cannot be frozen at all. TRM says the attacker still holds more than 420,000 ether and 18,270 bitcoin, worth billions of dollars, and no token issuer can stop them.[2]

Who Got In

Binance's first explanation was a compromised DevOps engineer's laptop, the machine of someone who runs its infrastructure. That was only its initial finding, not the full picture.[6][7] It said that laptop let the attacker reach a service container, a packaged piece of server software, and submit unauthorized withdrawal transactions.[9] Co-CEO Richard Teng rejected the simple version: the attacker did not just use one engineer's permissions, and this was not a single one-click action.[10]

TRM Labs attributes the attack, with high confidence, to TraderTraitor, which it calls North Korea's elite hacking unit.[2] Chainalysis says its strongest evidence was Binance funds commingling, in real time, with funds from last month's Bitget exploit, which had been attributed to North Korean actors. Investigator ZachXBT reported the same overlap.[2][3][11][12] Elliptic urges caution: only around $39,000 of Binance money reached the shared address, which may point to a shared launderer, not the same hacker.[3]

Elliptic adds that the slow stablecoin conversion breaks with typical North Korean laundering speed. No government or law enforcement agency has confirmed attribution.[3] The FBI says TraderTraitor targets company employees through social engineering, manipulating people rather than code. How this laptop was compromised remains undisclosed.[6][12] Binance pledged to cover all losses, from its user protection fund and its own money. It says it has set aside billions in company funds to do it.[1][8][9]

Autopsy Verdict

Binance's own account so far: a compromised engineer laptop may have given the attacker access to a service container, more points of breach have since been found, and there is no evidence of a key leak. TRM's best guess is that the signing system was made to sign for the attacker, but the root cause is still unconfirmed.[2][6][7][9] Our read: the damage outlasted the first blow, because the delegation behind it stayed in place through a sixth repeat sweep at 23:56 UTC.[2] Claimed by analytics firms, not governments: that North Korea's TraderTraitor did it, with Elliptic questioning how strong the link really is.[2][3][11]

Unknown: the exact total, with estimates from $5.912 billion to $6.43 billion, and whether those authorizations were phished or the signing system itself was compromised.[2][3][9] A freeze only works on a token with an issuer behind it. The ether and bitcoin the attacker still holds, worth billions by TRM's count, are beyond that reach.[2]

What to do

  • If you run hot wallets, alert within minutes whenever code appears at a treasury address that should have none.
  • Make signing systems refuse delegation authorizations unless they are expected, and treat a request for many at once as a sign of compromise.
  • Simulate every transaction before signing to see where funds would really go, and require a second, independent approval for anything unusual.
  • Cap how much each hot wallet can send per hour, keep freeze contacts with token issuers ready, and make sure revocation removes standing permissions.
  • Lock down engineer laptops with phishing-resistant sign-in and separate machines for production. For customers: after any exchange hack, ignore refund offers outside the official app.

Open questions

  • How was the DevOps engineer's laptop first compromised? Binance has not published its post-mortem or root cause.
  • What are the 'additional points of breach' Binance says it uncovered beyond the laptop?
  • What was the exact amount stolen? Estimates differ: $5.912B (Chainalysis initial), $6.3B (Binance), $6.36B (TRM), $6.4B (Chainalysis CEO) and $6.43B (Elliptic).
  • How many blockchains were affected: ten (TRM) or 11 (Elliptic)?
  • How much was frozen in total? Figures differ: about $2.7B (TRM), $2.84B (Elliptic) and about $3B (Binance). Will frozen funds be returned to Binance?
  • Will a government or the FBI officially attribute the theft to North Korea/TraderTraitor? Elliptic notes the overlap with Bitget is small and the laundering differs from past DPRK patterns.
  • Were the EIP-7702 authorizations phished, or was the signing infrastructure itself compromised? Did the attack involve multiple compromised devices?
  • Where will the roughly $2.4–3.3B in unfreezable ETH, BTC, XRP and other assets go next, and how much will be recovered?

Sources

  1. [1]The Record — Binance hit by record $6.3 billion crypto hack, scrambles to freeze funds
  2. [2]TRM Labs — North Korea Steals USD 6.36 Billion From Binance in the Largest Hack in History | TRM Labs
  3. [3]Elliptic
  4. [4]Cointelegraph — Binance hacked for over $5.8B in massive crypto exploit
  5. [5]BleepingComputer — Binance probes potential $5.8 billion crypto-theft hack
  6. [6]Cointelegraph — Binance hack may involve private key ‘misuse,’ not theft: Blockaid CEO
  7. [7]WIRED — The $6.3 Billion Binance Hack Was Pulled Off in Just 20 Minutes
  8. [8]Cointelegraph — Live updates: Binance $6.3B hack linked to North Korea’s TraderTraitor
  9. [9]The Hacker News — Binance Suffers Security Breach Affecting $6.3 Billion in Assets, Nearly $3 Billion Frozen
  10. [10]BleepingComputer — Binance links $6.3 billion crypto theft to compromised DevOps laptop
  11. [11]Chainalysis — Binance Exploit: Latest Findings and Response
  12. [12]Cointelegraph — North Korea’s TraderTraitor linked to $6.3B Binance hack
  13. [13]Cointelegraph — EIP-7702 didn’t cause Binance hack, but may have amplified losses