The Binance hack: what happened, what was frozen, and what it teaches
On 29 October 2026, an attacker drained 17 Binance hot wallets in under four hours. TRM Labs estimates USD 6.36 billion was stolen; Elliptic reports USD 2.84 billion frozen. Binance’s preliminary investigation identified a compromised DevOps engineer’s laptop, followed by additional points of breach. The findings point to a wider compromise of the withdrawal and signing infrastructure, with the full root cause still under investigation.
A breakdown of the attack, the freezes and the lessons for incident response, drawing on Binance’s official update, TRM Labs, Elliptic and other sources linked below.
How did the funds leave Binance?
The attacker gained the ability to submit withdrawals through Binance’s own hot-wallet signing system. Binance says it has found no evidence of private-key leaks. A compromised laptop was its initial finding; the subsequently reported additional entry points mean the incident cannot yet be reduced to a single device or individual.
Who is suspected?
TRM Labs and Chainalysis attribute the attack to TraderTraitor, a group linked to North Korea. Elliptic assesses North Korean involvement as likely. ZachXBT highlighted funds commingling with the earlier Bitget theft, a link discussed by the analytics firms. Shared laundering infrastructure is an indicator, not on its own proof that the same person carried out both attacks.
How the attack and freezing response unfolded
The attack was prepared for at least 36 hours and executed chain by chain in under four. The cited analyses place the first issuer freezes within an hour of the first drains, but response times varied by chain, asset and address. The frozen total alone does not show what had already moved or been converted before a restriction took effect. All times UTC.
- 28 OctStaging
The attacker's operator wallet is funded with three small Tornado Cash withdrawals. Attack code is deployed on 29 Oct and rehearsed on test wallets; the sweeper contract is deployed at 15:59.
- 20:04–20:16First drains: XRP Ledger, Solana, Optimism, Base
Five Binance XRP wallets send 233.46M XRP to one address, leaving each with its minimum balance.
- 20:20Bitcoin, TRON and the Ethereum setup – in the same minute
18,270 BTC leaves one hot wallet and is split immediately into 19 addresses. TRON loses 612.7M USDT and 46.4M TRX. On Ethereum, one transaction carries 50 pre-signed EIP-7702 authorizations for the "Binance 14" hot wallet.
- 20:24Main Ethereum sweep
167,464 ETH, 1.615B USDT and 62 other tokens leave Binance 14 in one transaction; Binance 16 sends 28,005.6 ETH. At 20:41, 780M USDC is pulled from a Binance smart account that Binance 14 controlled.
- 20:57–21:04The first freezes
World Liberty Financial blacklists WLFI tokens (20:57). Tether freezes 971.1M USDT (21:01). Circle freezes 823M USDC (21:04). Meanwhile, the attacker races to convert stablecoins into ETH, accepting losses of 12–26%.
- 21:42–23:35More freezes; withdrawals paused
Ripple freezes RLUSD (22:01). WLFI freezes USD1 (22:10). Aave freezes its markets (22:32). Binance pauses withdrawals (~22:33) and reports USD 2.54B frozen (23:35). A second wave hits Avalanche and Polygon (23:05).
- 00:08–00:52Containment
Arbitrum's Security Council force-moves 8,426 ETH and 74.6M ARB out of the attacker's wallet. Binance revokes the EIP-7702 delegation at 00:10:35 and reports about USD 3B frozen.
- 30 OctRoot cause and recovery
02:25 – Binance: total impact ~USD 6.3B; initial vector a compromised DevOps engineer's laptop. Later that morning – Binance reports "additional points of breach" and says its investigation is continuing. Reuters reports the FBI and US Secret Service are working with Binance (unnamed source).
How the attack worked
Inside the signing system
Binance's preliminary finding: a compromised DevOps engineer's laptop gave access to an internal service container, from which unauthorized withdrawals were submitted to Binance's own signing system. Binance says it has found no evidence of private-key leaks, and later reported "additional points of breach".
The EIP-7702 trick
Since Ethereum's Pectra upgrade (May 2025), a normal wallet can delegate its execution to a smart contract. Binance 14's nonce kept moving, so the attacker pre-signed 50 authorizations for 50 consecutive nonces. One matched, and the wallet forwarded incoming funds to the attacker for nearly four hours.
Plain transfers everywhere else
On the other 16 wallets there was no contract trick, just ordinary signed transfers. TRM Labs: the attacker most likely "gained the ability to make Binance's hot wallet signing system sign transactions across chains".
Frozen vs. on the move
Elliptic’s 30 October update reports USD 6.43 billion stolen and USD 2.84 billion frozen. On that basis, USD 3.59 billion was not reported frozen. This is a snapshot of the reported freeze status, not a live inventory of attacker holdings.
$2.84B · 44.2%
Reported frozen
$3.59B · 55.8%
Not reported frozen
What could happen to the remainder?
In comparable thefts, funds are split or consolidated, swapped into other assets, moved across bridges, and routed through mixing or cash-out services. Similar routes could be used here as the investigation continues. These are possible next steps, not a claim that every route has already been used in this case.
Chainalysis reports that part of the stolen stablecoins was rapidly swapped into ETH before freezes took effect. That illustrates the pressure on responders: tracing can continue after a swap, but the available ways to stop the funds can change.
Who froze what
| Who | What | Source |
|---|---|---|
| Tether | ~1.76–1.77B USDT across 11 wallets (Ethereum, TRON, Avalanche, Polygon); 6 were already empty when the freeze landed. Also 12,574 XAUT (gold token, ~$50M). As funds moved on, Tether blacklisted each new hop wallet within minutes (21:12–21:19 UTC). | TRM, Bitquery, Etherscan flow |
| Binance (WBETH) | 29,934 WBETH (~$75M), blacklisted at 22:48:35 UTC in the attacker wallet it had been moved to | Etherscan flow |
| Circle | ~823–825M USDC, frozen with law enforcement | TRM, Circle |
| Ripple | 40.5M RLUSD in the attacker's wallet (account paused at 22:00:59 UTC) + RLUSD in the compromised hot wallet; Binance credits Ripple with stopping ~$200M in total | TRM, Yi He, Etherscan flow |
| World Liberty Financial (with BitGo) | 27.8M USD1 + ~48.5M WLFI tokens (~$2–3M) | TRM, Bitquery |
| Paxos | 1,906.67 PAXG | Paxos |
| First Digital | ~3.45M FDUSD (a later transfer of it reverted) | Cointelegraph, Etherscan flow |
| Synthetix | 8.41M SNX (~$1.5M) pulled back from the attacker's wallet by the Synthetix protocolDAO, to be returned to Binance | Etherscan flow |
| Merit Circle (BEAM) | 984M BEAM burned in the attacker's wallet | Etherscan flow |
| Arbitrum Security Council | 8,426 ETH + 74.6M ARB (~$30.5M), force-moved to a locked wallet | TRM, Bitquery |
| Aave | Froze V3/V4 markets after the attacker borrowed 19,762 WETH against 60M USDT | Aave |
| Total | $2.84B reported frozen by Elliptic (freeze snapshot ~07:00 UTC; update 08:00 UTC on 30 October). Its total is a separate source snapshot, not a sum of every action listed here. | Elliptic |
Why some assets can be frozen
Tokens such as USDT and USDC have issuer controls that can restrict transfers from designated addresses. Native BTC and ETH have no equivalent issuer-operated blacklist. A receiving exchange may still be able to hold a deposit, while some networks and protocols have separate emergency powers. These are different intervention mechanisms, which is why the table distinguishes token freezes, protocol actions and funds moved into custody.
What the frozen total does not show
A successful freeze records the assets still reachable when a restriction takes effect. It does not show how much had already left the address, crossed a bridge or been converted into an asset without an issuer-level freeze function. A blacklist applied after such a conversion may restrict future token activity at that address without immobilising the ETH already received.
To assess response speed, a timeline needs to distinguish the theft, the arrival at each destination, any bridge transfer or swap, and the moment a blacklist takes effect. Transaction timestamps show the on-chain sequence. They do not, on their own, establish when an issuer first received an actionable alert or completed the checks required to act.
Why the sequence matters: Avalanche → Ethereum
The reported sequence places a USDC blacklist roughly an hour after funds crossed from Avalanche to Ethereum, with the funds already converted into ETH. It illustrates why a later token restriction may not stop assets that have changed form:
What this means for the industry
Tracing is a starting point. Action depends on time and coordination. An investigation needs to reach the exchange, issuer or law-enforcement team able to act while funds remain within reach. The reported freezes show what cooperation can achieve; the funds that moved first show why the response must also be assessed by what escaped intervention.
Preparedness means having clear escalation routes, usable evidence and relationships across jurisdictions before an incident. The same access should be available to smaller organisations and individual victims. Faster reporting and cross-border procedures should not depend on privileged access to industry contacts.
Europe needs working relationships beyond Europe. As we described in our October newsletter, Roman Bieda spent four days at an INTERPOL cybercrime event in Asia, where Tether was also represented. Such discussions help connect Recoveris’s European base with investigators, law enforcement and industry counterparts where stolen assets may move. This is the practical value of public-private cooperation: getting evidence to people who can assess it and act.
Recoveris supports that work through investigation, evidence preparation and coordination alongside institutions and their legal teams. A freeze preserves an opportunity; returning assets still requires the appropriate legal and operational steps.
Beware of compensation and recovery scams
A major theft creates an opening for follow-on scams
Beware of fake Binance support employees. Scammers may impersonate support staff and offer a “Binance refund”, “SAFU compensation” or guaranteed recovery through social media, messaging apps, SMS or email.
Watch for spoofing: disguising a sender’s identity, such as an email address, caller ID or SMS sender name, to make a message appear to come from Binance. A familiar name or logo is not proof that a message is genuine.
Impersonators may ask you to pay a supposed “tax”, “release fee” or “verification fee” to unlock your funds, or request a seed phrase, private key or wallet signature. Treat these demands as scam warning signs.
Do not share a seed phrase or private key, pay to unlock a promised refund, or connect a wallet through an unsolicited message. Verify claims through Binance’s official app or website reached independently, rather than a link or contact supplied in the message. Check Binance’s official announcements. If you have already been targeted, preserve the messages, payment details and transaction IDs for your report.
If your institution is hit
Recoveris helps exchanges, banks and VASPs trace stolen assets, prepare evidence and coordinate freeze requests with relevant platforms and law enforcement. The available steps depend on the assets, where they move and which organisations can act.
Discuss an incident with our team
Contact us about an active incident or preparations for a future response.
Media enquiries
For media enquiries about this analysis or to arrange a conversation with the Recoveris team, contact [email protected].
Sources and updates
Official Binance updates
Research and on-chain analysis
- Elliptic – The largest theft in history: North Korea likely behind the $6.4 billion Binance hack (updated 30 Oct, 08:00 UTC)
- TRM Labs – North Korea Steals USD 6.36 Billion From Binance in the Largest Hack in History
- Chainalysis – The $6.4 Billion Binance Exploit: Tracing the North Korea Link
- Bitquery – Binance Hack: $6.3B Drained on 9 Chains, $2.7B Frozen (06:43 UTC)
- Blockaid – Binance hack analysis
- Aave – Binance Hot Wallet Exploit: Aave's Response
- Etherscan – Binance hot-wallet drain, 29 Oct 2026: fund-flow trace (86 addresses, 162 flows, six EVM chains)
- ZachXBT – Binance and Bitget funds commingled · Paxos – PAXG freeze
News coverage
- Reuters (via Yahoo) – FBI and US Secret Service working with Binance, source says
- CoinDesk – Hack drained wallets backing customer assets · Largest crypto hack to date · Reported North Korea link
- Cointelegraph – Live updates · TraderTraitor link
- Bloomberg – Stolen bitcoin likely "gone", Ballet says
- CNBC – What we know and what comes next · CNN – North Korea suspected · Forbes – $6.3B impacted
- NBC News – Largest heist ever · Axios – Binance halts trading · TechCrunch – Withdrawals paused · The Block – Market impact · Infosecurity – Record hack
- The Crypto Times – More breach points, withdrawals in 45 hours
Latest page update
– Restored the media contact section with [email protected]. The scam warnings and source snapshots are unchanged.
This page provides general information, not legal, financial or investment advice.