On-chain investigationBinance29–30 October 2026

Binance's hot wallets sent $6.3B to an attacker in under four hours. $2.7B is frozen. Most of the rest sits untouched in the attacker's wallets

Billions in crypto left the world's biggest exchange in a single evening. We followed every coin, chain by chain, to see how it got out and where it went.

At a glance
Between 20:04 and 23:56 UTC on 29 October, Binance's own withdrawal system signed away $6.3 billion from 17 of its hot wallets to an attacker, on nine chains. Binance says a compromised engineer's laptop let the attacker in, and that no private key leaked. Tether, Circle and Arbitrum, with four smaller issuers, locked $2.7 billion. The attacker swapped another $729 million of stablecoins before the freezes landed. At 06:43 UTC it still held about $3.2 billion, mostly ETH and BTC in wallets that have never sent a transaction.
$6.3B
Taken from Binance on nine chains
$2.7B
Frozen or rescued
$3.2B
Still with the attacker at 06:43 UTC
3 h 50 min
How long the attacker's code ran Binance's main Ethereum wallet
Key findingsEach line has its own share link
  1. $6.3B

    Left 17 Binance hot wallets on nine chains between 20:04 and 23:56 UTC on 29 October.

  2. 50 approvals

    Signed by Binance's system let the attacker's code run its busiest Ethereum hot wallet for 3 hours 50 minutes.

  3. $2.7B

    Locked by Tether, Circle, Arbitrum's Security Council and four smaller issuers. Six of Tether's 11 freezes hit wallets already emptied.

  4. $729M

    Of stolen USDT was swapped into ETH and TRX before Tether's freezes landed.

  5. 508,621

    ETH now held by the attacker, 2.5x the 200,630 ETH it took. The rest was bought with stolen stablecoins and tokens.

  6. $3.2B

    Still with the attacker at 06:43 UTC. We found none of it sent to a known exchange or a mixer.

01 · What happenedWhat happened in the Binance hack

On Thursday night, Binance stopped letting its users take money out. The world's biggest crypto exchange said it was looking into a security problem. By then, most of the money was already gone.

Binance is where millions of people buy and sell crypto. Like any exchange, it keeps its customers' coins in wallets it controls, and it pays out withdrawals from a few of those wallets that stay online all the time.

That evening, in under four hours, those wallets sent coins worth about $6.3 billion to new addresses on nine blockchains. Ethereum, Bitcoin and TRON took the biggest hits. Binance says a hacker got in through an engineer's laptop and used Binance's own withdrawal system to send the money out.

Bitquery traced each transfer with its blockchain data. We matched every drain to a Binance wallet and followed the money to where it sits now. Tether, Circle, Arbitrum and four smaller token issuers locked $2.7 billion. Most of the rest sits in wallets that have never sent a transaction. Dollar values are at the prices of the moment the coins left, and holdings are as of early on 30 October.

02 · The setupWhere an exchange keeps your coins

An exchange does not keep every coin online. Most sit in cold wallets, which are kept offline and are slow to reach on purpose. A smaller amount sits in hot wallets. These stay online, so the exchange's systems can sign a withdrawal from them in seconds, at any hour, without anyone touching a cold wallet.

Binance publishes the addresses of its wallets in a proof-of-reserves list, a public record that lets anyone check the exchange holds what its customers own. Each wallet drained that night carries the Binance proof-of-reserves label in Bitquery's address data.

Where an exchange keeps your coinsthe basics
HOW AN EXCHANGE HOLDS YOUR COINSCold walletskept offline, hold most coinsrefill the hot walletsnow and thenHot walletsonline, signed by theexchange's withdrawal systempay out every withdrawalYouyour wallet or anotherexchange29 October: the attackerfresh addresses onnine chainsEvery wallet drained on 29 October carriesBinance's proof-of-reserves label in ouraddress data.
Every drain on 29 October came from the hot wallets in the middle.

A hot wallet moves only when the exchange's withdrawal system signs a transfer. That system is what the hacker reached.

03 · The nightNine chains in under four hours

The first coins left on the XRP Ledger. Five Binance accounts there sent 233.5 million XRP to an account that had not existed a minute earlier. Solana followed five minutes later, then Base and Optimism, two networks built on top of Ethereum.

A quarter of an hour later, the three biggest drains began within minutes of each other. Binance's TRON hot wallet sent out 613 million USDT. Its main Bitcoin hot wallet sent 18,270 BTC, all in one block. On Ethereum, the hacker set a trap inside Binance's busiest hot wallet and sprang it four minutes later.

Nine chains in under four hours29 to 30 October
EACH DRAIN BY CHAIN AND TIME · CIRCLES SIZED BY DOLLARS · UTC20:0020:3021:0021:3022:0022:3023:0023:3000:0000:30Tether's first freezeWithdrawals pausedAttacker cut offXRP Ledger$300MSolana$96MBase$2.7MOptimism$4.8MTRON$628MBitcoin$1.48BEthereum$3.77BArbitrum$32MPolygon$10MCircle area is in proportion to the dollars taken in that drain, at the time.Ethereum: seven drains. The 20:24 circle also holds a second Binance wallet drained 24 seconds later.
The XRP Ledger went first. Ethereum's drains ran on for three and a half hours.

Ethereum lost the most by far, $3.8 billion from three Binance wallets. Nothing else came close. Drains there kept coming for three and a half hours, and the last one landed after Tether's first freeze and after Binance had paused withdrawals.

Ethereum lost the mosttheft-time prices
DOLLARS TAKEN BY CHAIN, AT THE TIME OF THE THEFTFrozen or rescuedNot frozen$0$1B$2B$3B$4BEthereum$3.77BBitcoin$1.48BTRON$628MXRP Ledger *$300MSolana$96MArbitrum$32MPolygon$10MOptimism$4.8MBase$2.7M* XRP Ledger: tied by timing, by how the transfers were built and by Binance's own total, not by a shared address.Frozen means locked by the token's issuer or rescued by Arbitrum's Security Council.
Teal is the part frozen by an issuer or rescued by Arbitrum's Security Council.
Time (UTC)What happened
29 Oct, 14:54The attacker's gas wallet gets about 1 ETH out of Tornado Cash
20:04First drain: the XRP Ledger
20:10Solana drain begins
20:20TRON and Bitcoin drains; the EIP-7702 notes land on Binance 14
20:24Main Ethereum drain: 167,464 ETH, 1.6 billion USDT and 62 other tokens in one transaction
20:30Arbitrum drain begins
20:57World Liberty freezes the WLFI in the main receiver, the first freeze of the night
21:01Tether's first freeze, on the main Ethereum receiver
21:04Circle freezes 823 million USDC
21:25Tether's CEO says more than 1.567 billion USDT is frozen
22:33Binance pauses withdrawals, according to press reports
23:05Polygon drain
23:56Last Ethereum drain
30 Oct, 00:10Binance cancels the EIP-7702 note
00:18Arbitrum's Security Council locks the attacker's ARB and ETH
02:25Binance publishes its first findings

The XRP Ledger account shares no address with the rest of the attack. But its transfers were built in the same unusual way as the others, with a higher fee than Binance's own payments that day. Binance's own estimate of the damage, around $6.3 billion, only adds up if those coins are counted.

04 · The break-inHow the hacker got in

Early on 30 October, Binance said its first look points to "a compromised DevOps engineer's laptop". That gave the hacker a way into one of Binance's internal services, where the hacker could "submit unauthorized withdrawal transactions". Binance said it found "no evidence of any wallet private key leak".

The chain fits that account. Every drain carries a valid signature from a Binance wallet. On 16 of the 17 wallets, Binance's system simply signed ordinary transfers to the hacker. Those transfers were built differently from Binance's normal ones, though. On Bitcoin they paid about twice the usual fee. On TRON and the XRP Ledger they used settings we did not see on any of Binance's own transfers that night. The signing was Binance's. The software asking for it was not.

On Ethereum the hacker went further. Since the Pectra upgrade last year, an Ethereum wallet can sign a note called an EIP-7702 authorization. It lets the wallet borrow a smart contract's code, a program that lives on the chain, and run it as its own. Four minutes before the main drain, the hacker's wallet sent in a batch of these notes for Binance 14, Binance's busiest Ethereum hot wallet. Each note only works when the wallet's transaction count hits one exact value, so the hacker brought 50, one for each count in a row. One of them matched.

Binance's own system signed every drainBinance's account and the chain
TWO WAYS OUT, ONE CAUSEBinance's withdrawalservice, reached througha compromised engineer'slaptop (Binance's account)50 signed approvalsEIP-7702, one for eachpossible transactioncountHot wallet runsthe attacker's codeBinance 14, Ethereumfrom 20:20:597 sweepstriggered by the attacker'sown wallet, 20:24 to23:56 UTCOrdinary signed transfersfrom 16 more Binance hot wallets: one more onEthereum, the rest on Bitcoin, TRON, XRP, Solana,Arbitrum, Polygon, Optimism and BaseFresh addresseson eight more chains00:10:35 · Binance revokes the approvaland the hook closes after 3 h 50 minBinance says it found no sign that a wallet's private key leaked.The chain shows valid signatures on every drain. It cannot show who asked for them.
On Ethereum, signed approvals let the attacker's code run Binance's busiest hot wallet.

From that moment the wallet ran the hacker's code. The hacker called it seven times over the next three and a half hours. The first call alone took about 167,000 ETH, 1.6 billion USDT and 62 other tokens in one transaction. Seconds later, a second Binance hot wallet signed nine transfers of its own.

Binance cancelled the note just after midnight UTC, almost four hours after it was set. More than an hour and a half of that came after withdrawals were paused.

The chain cannot show who asked Binance's system to sign. ZachXBT and the security firm Blockaid said North Korea was likely behind it, CoinDesk reported. Binance has named nobody and says it is working with law enforcement.

The hacker's Ethereum wallet got its first gas money, the coin that pays network fees, from Tornado Cash, a mixer that breaks the link between where coins come from and where they go. About 1 ETH came out of the mixer five and a half hours before the Ethereum drain, and smaller amounts the day before.

05 · The freezesThe race against the freezes

Stablecoins like USDT and USDC have an off switch. Their issuers, Tether and Circle, can freeze an address so that the tokens sitting in it cannot move until the issuer lifts the freeze. The hacker moved fast to stay ahead of that switch.

Tether's first freeze hit the main Ethereum receiver 37 minutes after the big drain, and by then 700 million USDT had already left it for two new wallets. From there the money ran down a chain of fresh wallets. At each step some of it was swapped, and the rest was passed on before the freeze arrived. Back at the start, later drains still sent another 204 million USDT into the frozen main wallet, where it is stuck too.

Six of 11 freezes hit empty walletsEthereum and TRON
EACH WALLET THAT HELD STOLEN USDT · WHEN IT HELD IT · WHEN TETHER FROZE IT · UTCUSDT inside the walletFreeze that locked moneyFreeze on an empty wallet20:2020:3020:4020:5021:0021:1021:20ETH 0x5227…2f8clocked 1,175METH 0x9749…c762frozen emptyETH 0x0ddf…697efrozen emptyETH 0x8d53…639afrozen emptyETH 0x811f…e84cnot frozenETH 0x77ed…c3ebnot frozenETH 0x7aa4…bfd1frozen emptyETH 0xaa24…54a0locked 175METH 0xccbe…a263frozen emptyETH 0xb171…c8c3locked 30MTRON TG5iBMQ…wvzsGilocked 313MTRON TPBkSj…KN4frozen emptyTRON TCzBTk…7Y62locked 66MAmounts in millions of USDT. Each wallet passed its USDT to the next one down the list, or swapped it.Bars run to the freeze where money was locked, otherwise to the moment the wallet was emptied.
Each wallet passed its USDT on, or swapped it, before the next freeze landed.

Tether froze 11 of the hacker's wallets on Ethereum and TRON. Six were already empty when the freeze landed. One wallet passed on 130 million USDT less than a minute before its freeze. On Polygon, a smaller amount of USDT was frozen later that night.

Circle froze the 823 million USDC in the main Ethereum wallet three minutes after Tether's first freeze, before any of it moved. Smaller issuers acted too. World Liberty froze its WLFI token in the main receiver at 20:57, before anyone else, and later its USD1 stablecoin, as Zach Witkoff confirmed on X. Tether's gold token, Paxos, Ripple and First Digital followed. Together these six token freezes locked about $132 million.

Just after midnight, Arbitrum's Security Council moved the hacker's ARB and ETH on that network into a locked wallet. The council is a group that can act for the network in an emergency.

71% of the stolen USDT is lockedstolen USDT
WHAT HAPPENED TO THE 2,488 MILLION USDT TAKEN ON ETHEREUM AND TRONFrozen by Tether1,759M USDTTurned into ETH495M USDTSwapped to TRX234M USDTEthereum and TRON combined. ETH includes a loan taken against 60M USDT on Aave.
The other $729 million was turned into ETH and TRX before the freezes landed.

In all, 1.76 billion USDT is locked, 71% of what was taken. The other $729 million got out first. On Ethereum it went through UniswapX and 1inch Fusion, swap apps where market makers fill big orders, and through Uniswap's own pools. Some went into Aave, a lending app, as collateral for a loan paid out in ETH. On TRON it was swapped on SunSwap, TRON's main swap app. Our audit of Tether's freezes explains how the blacklist works.

06 · The swapHow stolen dollars became ETH

The hacker took about 200,000 ETH from Binance. Hours later, it held more than twice as much. The extra was bought with stolen stablecoins and the other tokens it took. Many of those tokens went to a fresh wallet first and were then sold on Uniswap and other DEXes.

The attacker holds 2.5x the ETH it tookEthereum
ETH TAKEN FROM BINANCE AGAINST ETH THE ATTACKER HOLDS · 06:43 UTC0100K200K300K400K500K600KTaken from Binance200,630 ETHHeld by the attacker508,621 ETHbought with stolen stablecoins and tokensHeld = nine attacker wallets on Ethereum. Seven of them have never sent a transaction.
About 308,000 ETH was bought with stolen stablecoins and tokens.

Speed cost money. On the stablecoins it sold through UniswapX and 1inch Fusion, the hacker paid about 15% over the market price for its ETH.

The swaps also explain two figures that went round on X, $875 million in ETH and $234 million in TRX. Both counted coins the hacker had bought with stolen stablecoins, which is why they run well above what Binance lost in those coins.

07 · The moneyWhere the money sits now

When we last read the chains, at 06:43 UTC on 30 October, the hacker held about $3.2 billion. ETH and BTC make up most of it.

Most of what is left is BTC and ETHat 06:43 UTC
WHAT THE ATTACKER HOLDS AT 06:43 UTC · AT 06:30 UTC PRICES$0$0.4B$0.8B$1.2B$1.6BBTC$1.43BETH$1.14BXRP$294MTRX$227MSOL$95MOther$12MOther: POL, OP and VIRTUAL still in the attacker's wallet on Polygon, Optimism and Base.Frozen tokens are left out, including the gold tokens and WLFI locked in the main Ethereum wallet.
We found none of it sent to a known exchange, a mixer or a bridge.
ChainWalletHolds at 06:43 UTCSince the drain
Ethereum0x8532…43d4197,460 ETHNever sent a transaction
Ethereum0xc887…286a137,602 ETHNever sent a transaction
Ethereum0x897c…8df378,415 ETHNever sent a transaction
Ethereum0x5440…c94240,601 ETHNever sent a transaction
Ethereum0x79e7…544a34,280 ETHNever sent a transaction
Ethereum0x03b0…20ea17,260 ETHNew at 05:15 UTC, never sent a transaction
Ethereum0xc209…850a3,000 ETHNever sent a transaction
Ethereum0x5227…2f8c3 ETH, plus frozen stablecoins and gold tokensSent its ETH to a new wallet at 05:15 UTC
Ethereum0xa97b…8d10under 1 ETH, plus unsold tokensSent its ETH to a stash at 06:36 UTC
Bitcoin19 addresses, listed below18,270 BTCUnspent since 20:48 UTC
TRONTSpe5H…kyZ8A638.2M TRXNever sent a transaction
TRONTRBdWq…2PRki33.3M TRXSending TRX out to be swapped for USDT
XRP LedgerrK21t6…gfzMx233.5M XRPNever sent a transaction
SolanaAffzFD…yGigBEaU970,551 SOLNever sent a transaction

Seven of the Ethereum wallets have never sent a transaction, and they hold almost all the ETH. The Bitcoin sits in 19 addresses, most of them holding exactly 1,000 BTC each. The XRP and the Solana coins have not moved. On TRON, one wallet holds most of the TRX.

The hacker spent the early hours of 30 October pulling its ETH together. At 05:15 UTC the main receiving wallet sent 17,260 ETH to a new wallet. Between 05:27 and 05:36, four wallets the hacker had used to sell stolen tokens such as LINK and USDe sent 14,540 ETH into one of the stash wallets. At 06:36 the second receiving wallet sent 7,647 ETH into another. All of that ETH stayed in wallets we track.

The TRX is moving too. Since 02:45 UTC the second TRON wallet has sent out 11.4 million TRX, in more than 30 lots, to new addresses. We followed two of them. Each passes the TRX to one more new address, which swaps it back into USDT on SunSwap. The USDT then goes to two older wallets we could not identify. Unlike TRX, that USDT can still be frozen by Tether.

We still found no transfer to a known exchange, a mixer or a bridge. Anyone can watch these wallets with the Bitquery MCP. The addresses are listed at the end.

08 · The scaleThe biggest crypto hack on record

CoinDesk called it the largest crypto theft on record, and the numbers back that up. The previous record, the Bybit hack of February 2025, took about $1.5 billion. This one took about four times as much. Even now, what the hacker still holds is more than twice what Bybit lost.

About four times the Bybit hackvalue at the time
THE LARGEST CRYPTO HACKS, AT THE VALUE WHEN THEY HAPPENEDFrozen or rescuedTaken$0$1B$2B$3B$4B$5B$6B$7BBinanceOct 2026$6.32BBybitFeb 2025$1.50BRonin bridgeMar 2022$625MPoly NetworkAug 2021$611M mostly returnedEarlier figures are as reported at the time: Bybit by the FBI, Ronin and Poly Network by the press.
Bybit's figure comes from the FBI. Ronin's and Poly Network's come from press reports.

It is not the only exchange hack this autumn. Last month, about $387 million left Bitget on nine blockchains, and our Bitget hack trace followed it out. Last week, CoinDCX lost $16 million from wallets it was still using, as our CoinDCX hack report showed. Two smaller drains this week, at Polymarket and Predict.fun, also ran on valid signatures instead of broken code.

09 · What to doIf you use Binance

Binance says user funds are safe. It says it will cover all losses from its SAFU fund, an emergency pot it keeps for hacks, and from its own money. Deposits and withdrawals stay paused until its security checks are done, and it says it will publish an updated proof of reserves.

  • Rely only on Binance's official channels for updates. Scams follow big hacks.
  • Do not sign anything or send coins to anyone who contacts you about the hack.
  • When withdrawals reopen, check the address you withdraw to before you confirm.

10 · The methodHow we traced the Binance hack

We started from every wallet that carries the Binance proof-of-reserves label in our address data. We looked for large transfers to new addresses that night, then followed each one hop by hop. We timed each freeze against the moment the money moved on, and read the final balances straight from each chain at 06:43 UTC. Dollar values use the price at the time of each transfer.

The full histories are also sold as files on the Bitquery Data Store, as the Ethereum, Bitcoin, TRON, Solana and XRP Ledger datasets.

Limits on these findings

Transfers were read in full up to about 02:10 UTC on 30 October on Ethereum and about 02:40 on the other chains. Later moves by the attacker's main wallets were checked up to 06:43 UTC, when holdings were read from each chain. Anything later is not covered.

Dollar values use the price at the time of each transfer: ETH and major tokens every five minutes, other tokens once a day, BTC and XRP hourly. Three small Ethereum tokens had no price and count as zero.

The XRP Ledger and Solana drains share no address with the rest of the attack. They are tied to it by timing, by how the transfers were built and, for the XRP Ledger, by Binance's own total.

Freezes count only where we found the freeze on-chain: Tether, Circle, World Liberty, Paxos, Ripple, First Digital and the Arbitrum rescue.

The record shows that each drain was validly signed. It does not show who asked Binance's system to sign, or how.

Wallet owners come from address labels and on-chain behaviour, and may be incomplete.

11 · The recordThe addresses behind the Binance hack

0x28c6c06298d514db089934071355e5743bf21d60
0xdfd5293d8e347dfe59e90efd55b2956a1343963d
0xee7ae85f2fe2239e27d9c1e23fffe168d63b4055
0x7c8601d4645b93cea45f71e118a729332e6b5ca0
0x63e842b054bd624a465454d533c33f573e9c6fae
0xad99264d5532ae0dd04b2004eebda05f25657e70dacb764f7ac8d4ccd051298b
0x53bd38b816c23e74134786c29a8c18d792777998a3b9326047b583100e88e2f3
0xafbf94c92a8d749988411669fa14d4f8866d9b4420b4ebd299f28e958dac7209
0x5227f603c1ee34ce3c06efe6477003bdfccb2f8c
0xa97bf7836f8a08f9ed91d41453d371493fae8d10
0x8532fa14acaf483729c449b8458aeddb900543d4
0xc887af690e0301cd4edbbce8f8d31b4ec65b286a
0x897c80d1a9729e94460e2bd93178bd5215158df3
0x03b0ee5d82990cff1bda48651ac3e436d1a020ea
0x9edf86533e73658700c5dadb2432dd7bebb628dc0f5fe37991c241f537856071
0xe4f9070e1316de2988fc6f869fead8fb99cc74cd
bc1qm34lsc65zpw79lxes69zkqmk6ee3ewf0j77s3h
bc1q0mtc2f5agpkvlq6hhahmfr3hlr55kyfjhl2mnm
bc1qxrxujwxfnvz040jw76d26zhjdg5jura7hs968s
bc1qepc70u3u476vgvg3hfcwjgu4mecxe2uchs4lag
bc1qdfhmlrdvg4tm87zjl0vyf0xflp5ql50q3g88gw
bc1qnq6jj9jmlf3945m3l8s0kxnqehrsga300k8t3s
bc1qz8hdwv8gmml0u96dsvnzsagz6krjyzxmgxupdp
bc1q42flhayrzy3zh8lkyevw8qcjduurt9a35wlsyx
bc1q63qrfrpsg5hh0zzn3kp2xx9vljl7dq7tatsjxp
bc1q0ts8gaf9ht0rr4u02hr56f8thndqsc4kmkmfv3
bc1q2wvz0kcsn4hqmajwtey30ud27fl25w8pveznn6
bc1qalwnl7dtaa73fsq5tyn0ghfy3fgfpqkt69tca8
bc1qjwdw6vrzq4vf6hckutvx4ucj86awwv99mxnz7w
bc1qs3aej5tmcdz0vctz8y9rjcxtxg8v5385577s56
bc1qm2j6v3247khlwzxl7p9vqnfkghcllyhv9wjaat
bc1qs6xnmhar38z44g2za93pv8ygdcwurrh8l87w3v
bc1qf5cyvv9w50tx9xx9s3xwsne0z87wvjj9l8a35u
bc1qg3nrzpuvq2pxqx74tcrywr09dc208ze96n3t53
bc1qm8v88m5fy6kuq9myva2eemwycxqd3e0zcrs2l8
bc1qrg025e2pgx0rwya2kpgtj30972p64jt0hn6zyt
bc1qxg0l4p6xc50zuv9cl5f0l0wmaxjpg8wcy7s9ra
TDqSquXBgUCLYvYC4XZgrprLK589dkhSCf
TG5iBMQPrDzJJAUM8GMVBf1hRaJ1wvzsGi
TSpe5HC3PRD2svJcr1YoGszhHk2mtkyZ8A
rK21t6nGLy4MNDqhvy3pGwcLFy25qgfzMx
5tzFkiKscXHK5ZXCGbXZxdw7gTjjD1mBwuoFbhUvuAi9
AffzFDKZbyMiU11zmVBoAqD25ugpr7xoWWyRyGigBEaU
0x3e2bf1ac6bf0934bbba6456c341c2ecbced632d5
0x410af166c81f9c0f26cc19b4d970c984f526225eeea2aea169179856fd615f70
Run it yourself

Follow the Binance hack money in plain English

Every transfer in this story comes from Bitquery's blockchain data. The Bitquery MCP server puts that data behind an AI assistant, so you can ask where a wallet's money went, or which labels an address carries, without writing a query. The full history is also sold as files on the Bitquery Data Store, as the Ethereum dataset and the Bitcoin dataset.

Watch the attacker's ETH and BTC stashesTrace any wallet on Ethereum, Bitcoin, TRON or SolanaCheck an address against Bitquery's labelsSee when a stablecoin address was frozen
Explore Bitquery MCP →Transfers, events and balances from Bitquery's data and public nodes. Data read on 30 October 2026.
Legal disclaimer

This article is provided for informational and educational purposes only and reflects analysis of publicly available on-chain data as of the dates indicated. It does not constitute legal, financial, compliance, or investment advice, and nothing in it is a recommendation to buy, sell or hold any token or asset, or to use or avoid any exchange, wallet, bridge, protocol or service.

The findings describe transactions and balances observed on Ethereum, Bitcoin, TRON, the XRP Ledger, Solana, Arbitrum, Polygon, Optimism and Base on 29 and 30 October 2026. Attributions come from address labels and from on-chain behaviour; they may be incomplete or incorrect and may be revised as more data becomes available.

References to Binance, Tether, Circle, World Liberty Financial, Paxos, Ripple, First Digital, Arbitrum, Uniswap, 1inch, Aave, SunSwap, Tornado Cash, Bybit, Bitget, CoinDCX, Polymarket, Predict.fun, CoinDesk, Blockaid, ZachXBT or any other named project, company, service or person describe what the public record shows about addresses and transactions linked to them, and what those parties have said in public. They are not statements about any party's intent, security practices, solvency or conduct, and nothing here asserts that any named party acted unlawfully or negligently. The wallets that received the funds are described by their behaviour and attributed to nobody.

Nothing herein should be relied upon as a definitive determination of fact. Readers should conduct their own independent verification before taking any action. The authors and publisher accept no liability for any loss or damage arising from reliance on this material. All trademarks and company names are the property of their respective owners.

Reported by Gaurav Agarwal for Bitquery Research, with AI tools; every figure was checked against the raw data.

FAQ

How much was stolen in the Binance hack?

About $6.3 billion, at the prices of the moment it left. The coins came from 17 Binance hot wallets on nine blockchains on the evening of 29 October, in under four hours. Binance's own estimate is about the same.

How did the Binance hack happen?

Binance says a hacker got into its systems through a compromised engineer's laptop and used its withdrawal service to send money out. No private key leaked, Binance says. On Ethereum, the hacker also used EIP-7702 authorizations, signed by Binance's system, to make Binance's busiest hot wallet run the hacker's code.

Is Binance safe after the hack?

Binance says user funds are safe and that it will cover all losses from its SAFU fund and its own money. Deposits and withdrawals were paused while it checks its systems. It has promised an updated proof of reserves and a full report on what went wrong.

How much of the stolen crypto was frozen?

About $2.7 billion. Tether locked 1.76 billion USDT and Circle locked 823 million USDC. Tether's gold token and four smaller issuers froze about $132 million in other tokens, and Arbitrum's Security Council moved the hacker's ARB and ETH on its network into a locked wallet.

Where is the stolen money now?

Early on 30 October, the hacker held about $3.2 billion, mostly ETH and BTC. The biggest wallets have never sent a transaction, and we found none of the money sent to a known exchange, a mixer or a bridge.

Is the Binance hack the biggest crypto hack ever?

By the figures reported so far, yes. At about $6.3 billion, it is about four times the size of the Bybit hack, the previous record at about $1.5 billion.

Run the next investigation in minutes

Ask any question of the blockchain. Bitquery's AI Investigations agent traces funds, attributes wallets, and writes auditable reports across every major chain. Prefer to do it yourself? Connect the Bitquery MCP server to your AI assistant, pull the raw datasets, or query the chain directly with the Bitquery API.