Q3 2026 Security & Compliance$1.18B stolen across 107 incidents. Main drivers: supply chain, smart contracts, keys.
Get the report →

Lessons from Binance $6.3B hack analysis

31 min read

Binance lost $6.34B without losing a key

On 29 October 2026, an attacker stole $6.34 billion from Binance's hot wallets across 11 blockchains. The attack lasted less than four hours, from 20:05 to 23:56 UTC. It is the largest crypto theft on record, exceeding the previous record, the Bybit hack, by more than four times.

The breach was the result of a four-month operation targeting Binance employees and internal systems. It began with a tampered installer in June, followed by a fake job interview in September and access to an internal AI tool on 20 October. On the night of the attack, the attacker used a stolen token to deploy a container that sent unauthorized transfer requests to Binance's internal wallet signing service. The service approved them, allowing funds to move across all 11 networks. No private keys were stolen.

Binance and other parties froze or intercepted $2.85 billion, around 45% of the stolen funds, 94% of which was in stablecoins. Binance also replaced 98% of the stolen assets using its own funds and began reopening withdrawals in phases on 1 November. The attack has been attributed to North Korea's TraderTraitor group.

In this article, we'll overview the Binance incident, how it was executed, and what lessons security leaders should learn from it.

Incident overview
$6.36B
stolen
~20min
attack execution
44%
frozen

How did a job interview reach the signing service?

The exploit unraveled in five steps over four months: 

A caught compromise still exposed the wallet team

In June, a Wallet DevOps engineer, Engineer A, searched for a popular AI coding tool and installed a tampered copy of Homebrew. Binance's security team spotted it, replaced the device and rotated his credentials.

The attacker kept what it had already learned: Engineer A's role and the people he worked with on wallet infrastructure.

After a confirmed hit on a privileged team, treat the whole team as targeted and raise monitoring on every member.

An interview assignment replaced a developer tool

In September, Engineer B, whose profile on a legitimate job platform mentioned Binance, was invited to two interviews by a fake "Project Director": a live video call with an "HR representative" who shared a social media account full of personal photos to build trust, then a chat with a "CEO" of a company that doesn't exist. At the end, Engineer B downloaded a coding "assignment" to his work computer.

The repository ran code during setup. It replaced pyenv in the Homebrew directory with a malicious copy and opened a channel to the attacker. Endpoint protection didn't detect it.

Endpoint tools look for known bad behaviour. This was a legitimate developer tool swapped for a lookalike in a folder the user can write to. An integrity check on developer tooling would have caught it, and so would a rule that keeps outside code off machines with production reach.

If your engineers can run an interview task on the laptop that holds a deploy token, your hiring pipeline is part of your wallet perimeter.

An internal AI tool carried the attacker to two more machines

On 20 October, from Engineer B's computer, the attacker used an internal AI tool to take control of Engineer A's machine and a third engineer's, Engineer C on the wallet software team. Engineer A's computer held a container deployment token. How the tool was used stays confidential.

An internal tool that can act on other employees' machines is a privileged identity, whatever it's called. If it isn't in your privileged-access inventory, with its own approvals and logs, it's a lateral movement service you're running for free.

A deployment token on a laptop opened the signing service

On 29 October, between 17:15 and 19:56 UTC, the attacker logged on to Engineer C's computer, used Engineer A's credentials to deploy a container, and started the script that reached the internal wallet signing service. From there it initiated transactions outside the normal withdrawal process.

Two things failed here. A long-lived deployment token sat on a laptop. And the signing service signed for a caller in the right environment without checking each request against an approved withdrawal.

A signer that signs whatever an authorised caller sends works like a printer.

One signing service covered every chain

Five hot wallets on the XRP Ledger sent 233.46 million XRP to the attacker between 20:05 and 20:09. Wallets on Solana and Optimism followed with about 970,500 SOL and 44.2 million OP. Only then did Binance get an internal alert about large transfers.

Bitcoin, Tron and Ethereum went after that alert: 18,270 BTC, 612.7 million USDT and the $2.53B Ethereum sweep. Using per-chain values, about $5.9B, more than nine-tenths of the theft, left after Binance's first alert.

These chains use different key types and signing schemes. Once one service signed for all of them, the architecture set the blast radius. Here's how the sweep looked on the timeline:

Attack timeline by chain

  1. 20:05XRP Ledger$296M
  2. ~20:10Solana$96M
  3. ~20:10Arbitrum, Optimism, Base$39M combined, through ~20:36
  4. First internal alert at BinanceAbout $5.9B leaves after it
  5. 20:20Bitcoin$1.47B
  6. 20:21Ethereum$3.79B
  7. ~20:22Tron$628M
  8. ~20:36Avalanche$28M, including the second wave
  9. ~23:05Polygon and Avalanche againPolygon $10M

MPC protected the key and slowed the revocation

Multi-party computation keeps a key from being stolen, and here the key stayed put. In this case, MPC setup signed whatever the signing service asked it to sign, because the signing service itself was compromised.

On Ethereum the attacker had set an EIP-7702 delegation on a hot wallet, and only that wallet could sign the authorisation that removes it. Because the wallet used MPC, no single key could revoke it immediately, and the team had to build a procedure on the night.

Suspending withdrawals left the delegation in place, because it acted on-chain and worked outside Binance's withdrawal system. The last unauthorised transfer, 2,961.9 ETH, finalised at 23:56 UTC. Binance cleared the delegation at 00:10:35 on 30 October, 3 hours 46 minutes after the main sweep.

Rehearse an emergency revocation that doesn't depend on the system you suspect, and time it.

One signed delegation handed a hot wallet to the attacker

On-chain, the attacker prepared for 36 hours. An operator wallet received three small withdrawals from Tornado Cash on the morning of 28 October. The attacker tested its code on two wallets on the 29th, rehearsed the final version on a third and sent the test funds back. The program that later emptied a Binance wallet was deployed at 15:59 UTC, about four hours before the attack.

EIP-7702 lets an ordinary wallet lend its permissions to a smart contract. The wallet signs an authorisation, and from then on the contract's rules apply whenever anyone uses the wallet. It stays in force until the wallet signs a new one.

The attacker's contract is a sweeper. The sweeper takes everything out of a wallet, sends it to the attacker and takes orders from one address only. The target was Binance 14, one of Binance's best-known hot wallets. The authorisation had to be signed by Binance 14 itself, and Binance's signing service signed it.

Fifty authorisations covered an unknown nonce

Each authorisation is valid for one nonce, the count of transactions the wallet has sent. Binance 14 was busy paying out withdrawals, so nobody could know which count it would be at when the authorisation landed. The attacker had the signing service sign 50 consecutive nonces, 18,914,775 through 18,914,824, and sent them in one transaction at 20:20:59. Nonce 18,914,809 matched, and the other 49 were discarded.

Fifty authorisations for one wallet, over a range of nonces, in one batch, is an easy pattern for a signer policy to refuse. A policy that refuses unexpected EIP-7702 authorisations would have refused all 50.

Nonce window

50 signed1 valid
775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824
one signed authorisation per nonce, last three digits of 18,914,775 to 18,914,824
809 matched the wallet's nonce34 already used15 not reached yet

The sweep was visible for 17 blocks

At 20:24:23, three minutes and 24 seconds after the delegation landed, the attacker told the wallet to send out everything it held: 167,464 ETH and 63 tokens, including more than 1.6 billion USDT, worth $2.53B. For those 17 blocks, the delegation was visible to anyone who read the wallet's code.

The sweeper then stayed in place until the reset, picking up funds that arrived later, including 780 million USDC pulled from a linked Binance smart account at 20:41. Ripple and World Liberty Financial froze their tokens inside the compromised wallet, which stopped new deposits of those tokens from being taken.

A check of eth_getCode on every hot address, every block, would have flagged the delegation 17 blocks before the sweep.

Binance 14 account changes

@@ code at 0x28C6…1d60, block 26,300,753, 20:20:59 UTC @@
−0x # no code: an ordinary wallet
+0xef0100 63e842b0…6fae # now points to the attacker's sweeper
@@ next 17 blocks, 3 min 24 s @@
 # visible to anyone who calls eth_getCode
@@ balance, block 26,300,770, 20:24:23 UTC, sweep() @@
−167,464.25 ETH and 63 tokens, including 1,615,409,498.97 USDT
+1 ETH # the sweeper leaves 1 ETH in the wallet
@@ code, 30 Oct, 00:10:35 UTC, new authorisation signed by Binance 14 @@
−0xef0100 63e842b0…6fae
+0x # delegation reset, 3 h 46 min after the sweep
Under EIP-7702 the account code becomes 0xef0100 plus the delegate address and stays until the account signs a new authorisationDelegation tx ↗ Reset tx ↗

Check the Ethereum transactions yourself

The attacker's operator address is 0x7C86…5CA0 and the sweeper contract is 0x63e8…6fAe. The sweeper's published source shows that only the operator address can give it orders.

Stablecoins decided how much could be recovered

Of the $6.34B taken, $2.85B was frozen or intercepted. Four assets made up 74% of the theft: USDT on Ethereum, BTC, USDC and USDT on Tron. Stablecoins were 54% of what was stolen and 94% of what was frozen.

Tether froze 1.77B USDT, the first of it at 21:01 UTC, 37 minutes after the Ethereum sweep. Circle froze more than $1.1B in USDC, Ripple 40.5M RLUSD and World Liberty Financial 27.8M USD1. The Arbitrum Security Council moved 8,426 ETH and 74.6M ARB out of the attacker's reach at 00:08, and Optimism's governance moved 44M OP on 31 October.

Freezes after the sweep

sweep+1 h+2 h+3 h+4 h+5 h
Tether1.77B USDT
21:01
21:01
CircleOver 1.1B USDC
21:04
21:04
Ripple40.5M RLUSD
22:01
22:01
World Liberty Financial27.8M USD1
22:10
22:10
Arbitrum Security Council$30M in ETH and ARB
00:08
00:08

How the attacker raced the freezes

About $786M of stablecoins became ETH and TRX before the issuers acted, including 434M USDT sold for 160,451 ETH at a 12–26% loss. One wallet borrowed 19,762 ETH on Aave against 59.9M USDT. On Tron, 234M USDT was swapped for 638M TRX.

About $3.25B in unfreezable assets are now spread across more than 800 attacker addresses: about 584,000 ETH, about 18,300 BTC and 233 million XRP. The bitcoin hasn't reached a service. About $242M left Tron in two days through Relay, THORChain, Chainflip and Symbiosis. Services were asked to block 608 Ethereum addresses, 19 Bitcoin addresses and one Solana address tied to the theft.

Aftermath: Binance covered the loss from its own funds

Binance set aside more than 100% of the loss and has replaced 98% of the stolen assets from its SAFU fund, its futures insurance fund and its corporate treasury. Its zero-knowledge Proof of Reserves for BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC, on a 31 October snapshot, was completed on 2 November and later extended to 44 tokens. Withdrawals reopened in phases from 06:00 UTC on 1 November, and net outflows that day were $3.64B, 2.1% of its assets.

Binance rebuilt the affected wallet system and the internal AI tool, replaced the affected devices, retired the engineers' credentials and tokens, scanned every employee device, tightened wallet-service risk controls and brought in outside security firms for an independent review.

Six controls that break this chain

Each control maps to a step above and works whatever tools the attacker brings. Each one is a test you can run against your own stack. Binance's controls each worked on their own, and the attack went between them. Testing them one at a time keeps that gap out of sight.

Six places to break the chain

1Untrusted code on work machines
September: an interview assignment ran on a work computer and replaced pyenv, and endpoint tools missed it
Run interview tasks and third-party repositories in disposable sandboxes, never on machines with production access
2Developer tool integrity
June and September: a tampered Homebrew install, then a swapped pyenv binary
Pin and verify the developer toolchain, and alert on any change to package-manager binaries
3Internal AI tools
20 October: an internal AI tool gave the attacker control of two more engineers' machines
List what each AI tool can reach, scope it like a privileged account and log every action it takes on another machine
4Deploy tokens on laptops
29 October: a container deployment token on a laptop let the attacker deploy into the wallet environment
Issue short-lived, device-bound tokens and deploy only through a pipeline with approval
5Signer policy
20:05 to 20:36: one signing service signed transfers outside the withdrawal process on every chain, plus 50 EIP-7702 authorisations for one wallet
Make the signer refuse anything it can't match to an approved withdrawal and any unexpected EIP-7702 authorisation, and split signers by chain and wallet tier
6Alert to stop, stop to revoke
20:10 to 00:10: about $5.9B left after the first alert, and the delegation stayed 3 hours 46 minutes after the sweep
Watch eth_getCode on every hot address each block, and drill the time from alert to signer stopped and to on-chain revocation through a path that doesn't rely on the suspect system

Test the path from a laptop to your signer

Hacken's red team runs this scenario end to end, from social engineering and developer machines to CI/CD, containers and wallet and key management, mapped to MITRE ATT&CK and aligned with DORA threat-led penetration testing. You get an attack narrative with the decision points where your own chain breaks.

Request a red team assessment

Have questions?

See how Hacken can help you with readiness for governance frameworks, regulatory evidence, and security reviews.

Talk to expert
Banner Image

Subscribe to our newsletter

Be the first to receive our latest company updates, Web3 security insights, and exclusive content curated for the blockchain enthusiasts.

Speaker Img