On-chain investigationBinance hackWho profited

The Binance hacker lost $119M to bad prices while cashing out. Traders kept $60M. Block builders and validators took $30M

Each hurried swap left money on the table for whoever stood on the other side. We tracked who that was, wallet by wallet, on Ethereum and TRON.

At a glance
On the night of 29 October, the Binance hacker swapped stolen coins in a rush and lost $119M against market prices. Most of it came from overpaying for ETH on Ethereum, where Uniswap's main pools ran up to 38% above the market. Traders and their bots sold into those pools and kept $59.9M after costs. The bots paid $29.5M to Ethereum's block builders and validators to trade first.
$119M
Lost by the hacker to bad prices
$60M
Kept by traders and their bots
$30M
Paid to block builders and validators
38%
Peak ETH markup on Uniswap
Key findingsEach line has its own share link
  1. $119M

    Lost against market prices by the hacker who robbed Binance, swapping stolen coins in a hurry on 29–30 October.

  2. $60M

    Kept by traders and arbitrage bots after gas and builder tips. They sold to the hacker high and bought its tokens cheap.

  3. $30M

    Paid to Ethereum's block builders and validators by bots racing to trade first. Builders passed most of it to validators.

  4. 38%

    How far ETH on Uniswap's main WETH/USDT pool rose above the market at 21:09 UTC, as the hacker bought.

  5. $24.8M

    Given up dumping stolen tokens such as UNI, PEPE and ENA below market. Block builders took 49% of it.

  6. $3,185

    All the hacker could withdraw from its unfrozen Aave deposit on the morning of 30 October, because Aave's USDT pool was nearly empty.

01 · What happenedWho made money from the Binance hack

The Binance hacker had a problem. Much of the haul was in digital dollars that their issuer could freeze. So on the night of 29 October, the hacker raced to swap them for ETH and TRX. Speed cost money.

Every rushed trade paid well over the going price, and every stolen token sold went for less than it was worth. Add up the night and the hacker lost $119 million against market prices. Each of those dollars landed with someone on the other side of a trade.

Bitquery records every trade on Ethereum and TRON, so we followed that money to where it ended up. Trading firms and their bots kept $59.9M after their costs. The builders and validators who put Ethereum's blocks together took $29.5M, paid to them by the same bots racing to trade first. We could not trace about 4%. Our trace of the Binance hack covers the theft itself: how $6.3 billion left Binance and where it sits.

02 · The setupWhy a hurried trader pays everyone else

Most crypto swaps on Ethereum happen in pools. A pool is a pot of two coins run by code, and the price comes from the mix inside the pot. A large buy takes one coin out, so its price in that pool rises with each trade.

When one pool's price drifts away from the rest of the market, arbitrage bots move in. They buy ETH where it is cheap and sell it into the pool where it is dear, until the two prices meet again. Traders call this crypto arbitrage, and on a normal night the gaps are tiny. Our piece on arbitrage that makes 69 cents a trade shows how thin they usually are.

Bots compete for the same gap, so they pay to go first. On Ethereum they tip the block builder, the firm that orders transactions into each block. The builder passes most of it on to the validator who adds the block to the chain. Traders call this race MEV, short for maximal extractable value.

The hacker also used two order apps, UniswapX and 1inch Fusion. On both, you sign an order and a trading firm fills it from its own stock or from pools. UniswapX calls these firms fillers; 1inch calls them resolvers. Our study of CoW Swap's solver auctions explains how firms compete for such orders.

03 · The lossesWhere the hacker lost $119M

The hacker lost $119M to bad pricesagainst market prices
WHERE THE ATTACKER LOST $119M AGAINST MARKET PRICESETH bought over market on Ethereum$71.5MStolen tokens sold below market$24.8MTRX bought over market on TRON$22.4MRLUSD sold below $1$0.3MMarket price: Hyperliquid, minute by minute. Stablecoins at $1.
Most of it came from buying ETH in a hurry on Ethereum.

Buying ETH cost the most. The hacker swapped stolen USDT for ETH through the two order apps and then straight from pools, and paid $71.5M more than the coins were worth on the open market. Selling stolen tokens such as UNI, PEPE and ENA below their market price cost another $24.8M. Buying TRX on TRON cost $22.4M.

These are losses against a fair price, measured trade by trade. The hacker still holds the ETH and TRX it bought. It got fewer coins, or fewer dollars, than an unhurried trader would have. Another 56 small tokens had no reliable market price to compare with; against their price before the hack, the hacker gave up about $9–16M on those, which is not in the total.

04 · The winnersWho ended up with the money

Traders kept half, block builders a quarterwho got the money
WHO ENDED UP WITH THE $119MTraders and arbitrage bots, after costs$59.9MBlock builders and validators$29.5MLiquidity providers$20.2MUniswapX fillers, 1inch resolvers$6.7MNot traced or not split$4.5MBurned as gas$1.9MAggregator fees$0.3MTraders who paid the high price−$4.1MTraders' figures are after their gas and builder tips. The last row lost money buying at the high prices.
Traders kept their share after paying gas and builder tips. Liquidity providers are counted at the prices of the moment.

Half of it went to traders. Most were arbitrage bots that sold ETH and TRX back into the overpriced pools or bought the dumped tokens cheap, and some were large holders who sold at the right moment. Their $59.9M is what they kept after paying gas and builder tips.

A quarter went to Ethereum's block builders and validators: bots paid them $29.5M in tips and fees to have their trades placed first.

Liquidity providers, the people who deposit the coins a pool trades, booked $20.2M at the prices of the moment. Most of the TRON share came from TRX's market price rising toward the pool price later in the night. Against simply holding their coins, TRON's liquidity providers were ahead by only $0.74M by morning. The fillers and resolvers that took the hacker's first orders kept $6.7M.

05 · EthereumOn Ethereum, ETH sold at a 38% markup

The hacker started with the order apps and paid a 16% markup on them. Fillers and resolvers took the stolen dollars and delivered ETH at prices well above the open market.

How the hacker bought ETHPaidGotOver market
UniswapX and 1inch Fusion orders, 20:34–20:49 UTC325M USDT122,316 ETH at $2,657 each (market $2,284)$45.7M
Straight from pools, mainly 21:04–21:09 UTCUSDT and USDCETH$25.8M

The fillers bought much of that ETH from pools, which pushed pool prices up. Then the hacker's own wallets bought from the pools too, and two of them alone overpaid by $21.9M. In Uniswap's main WETH/USDT pool, the minute-average price of ETH peaked 38% above the market.

ETH on Uniswap ran up to 38% over the marketEthereum, minute by minute
ETH PRICE ON ETHEREUM'S BIGGEST POOLS VS THE MARKET · 29–30 OCT · UTCUniswap WETH/USDT poolUniswap WETH/USDC poolMarket price (Hyperliquid)$2,200$2,400$2,600$2,800$3,000$3,20021:0022:0023:0000:0001:00
The market line is Hyperliquid. Pool prices are one-minute averages of every trade.

The gap drew in arbitrage bots from all over Ethereum. Thousands of wallets sold ETH into the high pools before the gap closed, and they kept $40.7M after gas and builder tips. Bots took $28.7M of that. The rest went to wallets that traded a few times or once, and some of them sold thousands of ETH in a single trade.

Where the ETH overpayment wentEthereum
HOW THE ETH OVERPAYMENT MOVED ON ETHEREUMThe attackeroverpaid $71.5MUniswapX and 1inch orders$45.7M over marketBought straight from pools$25.8M over marketDEX pools pushed upup to 38% over marketSellers and bots$40.7MBuilders, validators$18.2MFillers, resolvers$6.6MLiquidity providers$4.8MBurned as gas$1.7MFillers kept part of the order premium; the rest was paid into the pools and taken back out by sellers.
Sellers and bots are counted after their gas and builder tips.
WalletGain before costsGas and tipsKeptTrades
0x0cdd…61d8$3.49M$0.03M$3.46M26
0xcb02…1d1d$1.73M$0.01M$1.72M2
0x65a8…7675$0.89M$0.01M$0.88M65
0xcaab…ec1e$0.88M$0.01M$0.87M14
0xb7c8…dd20$0.90M$0.06M$0.85M45
0xa127…3fa6$0.72M$0.00M$0.72M2
0x09df…e86b$0.67M$0.02M$0.66M12
0x58a4…e836$1.26M$0.67M$0.59M25

None of the top wallets carries a firm name in address labels. The largest, 0x0cdd…61d8, made $3.46M in 26 trades and paid no builder tips at all. CoW Protocol's settlement contract shows up too: it carried $1.27M of gains for users who swapped through CoW Swap that night.

Most of the fillers' $6.7M came from a single order. One 1inch resolver paid for its ETH with a loan from Compound instead of buying from pools, and kept about $6.1M. The fillers that bought from pools passed most of their margin to the pools and to block builders.

06 · The MEV raceMEV bots paid Ethereum's block builders 10,251 ETH

Bots paid builders 10,251 ETH in tipsEthereum block builders
ETHEREUM BLOCK BUILDERS, 20:30–01:00 UTC · HACK NIGHT VS THE NIGHT BEFORE · ETHHack nightNight beforeTips sent to builders10,251 ETH4.6 ETHPriority fees1,574 ETH13.3 ETHGas burned1,694 ETH2.9 ETHWhat builders did with itpaid on to validators, about 11,217 ETHkept about 564 ETHTips are payments from trading bots to the builder of the block. All Ethereum blocks in the window.
All Ethereum blocks from 20:30 to 01:00 UTC, against the same hours the night before.

On the night before the hack, bots sent Ethereum's block builders 4.6 ETH in tips over the same four and a half hours. On the hack night they sent 10,251 ETH. Every bot wanted to be first to the gap, and the only way to jump the queue was to pay more than the next bot.

The builders kept little of it, about 564 ETH. They paid the rest on to the validators who proposed their blocks, mostly through Titan's payment relay. Validators run by staking pools such as Lido share that income with their stakers. Failed attempts cost money too: 10,235 transactions failed that night, against 3,500 the night before, and each one still paid gas. Our look at why Ethereum staking yields halved explains how this kind of income reaches stakers.

07 · TRONOn TRON, the pool stayed high all night

On TRON, the hacker swapped 234 million USDT for TRX on SunSwap and paid well over the market for every coin. SunSwap's main TRX pool jumped to 18% above the market, and the gap never fully closed.

SunSwap stayed above the market for ten hoursTRON
TRX PRICE ON SUNSWAP VS THE MARKET · 10-MINUTE AVERAGES · UTCSunSwap WTRX/USDT poolMarket price (Hyperliquid)$0.32$0.34$0.36$0.38$0.4022:0000:0002:0004:0006:00
The hacker paid $0.367 per TRX on average, against about $0.33 on the market. The pool line is a 10-minute average of trades in the main WTRX/USDT pool.

Traders who sold TRX into the pools made $12.4M before fees. The top wallet, which trades through the contract TS5v9Z…NZC7, made $1.11M by buying TRX in one pool and selling it in another within the same transactions.

WalletGain before feesTransactions
TUAAqY…qrSS$1.11M34
TVFxAQ…wAoc$0.92M575
TDR4JC…Gsui$0.75M38
TActor…XdK4$0.72M281

The pool's liquidity providers look like big winners at first sight, at $10.4M. Most of that came from TRX's market price rising about 9% toward the pool price later in the night. Against simply holding their coins, they were up $0.74M by morning.

The hacker has started selling. Early on 30 October, 15 new wallets funded through the hacker's TRON addresses sold 8.9 million TRX for $3.1M of USDT, into pools that were still slightly above the market. The largest TRX stash had not moved. The full TRON history is also sold as files: the TRON dataset on the Bitquery Data Store.

08 · Token dumpsDumping stolen tokens cost the hacker $24.8M

Later that night, the hacker's wallets began selling the other tokens taken from Binance: UNI, PEPE, ENA, LINK, AAVE and dozens more. On the tokens with a reliable market price, the hacker received $208M, which was $24.8M less than the coins were worth at the time.

Dumping stolen tokens cost the hacker $24.8Mtoken sales on Ethereum
WHAT THE ATTACKER GAVE UP ON EACH DUMPED TOKEN · TOP 10UNI (11% below)$5.0MPEPE (9% below)$3.3MENA (8% below)$3.1MUSDe (30% below)$2.9MONDO (20% below)$1.7MLINK (5% below)$1.3MAAVE (7% below)$1.1MWLD (7% below)$0.5MAPE (49% below)$0.5MZRO (9% below)$0.4MDiscount = value at the Hyperliquid price in the same minute, minus what the attacker received.
Each bar compares what the hacker received with the Hyperliquid price in the same minute.

The worst sale, as a share of value, was USDe, Ethena's dollar token. The hacker sold it into a small pool and took a 30% haircut, about $2.90M. Our report on the USDe loop unwind covers how that token usually trades.

Who caught the discount? On the biggest tokens, block builders took 49% through bot tips and priority fees. Bots kept $4.9M and liquidity providers $5.1M. Some of the best-known bots spent more than they made.

Bot or firmWalletDiscount caughtPaid to buildersKept
Unnamed bot0x0000…b599$2.07M$1.14M$0.92M
UniswapX filler from section 050xbeef…c555$0.24M$0.14M$0.09M
Wintermute (labelled contract)0x51c7…2a7f$0.56M$0.46M$0.08M
jaredfromsubway (MEV bot)0xae2f…ae13$2.87M$2.95M−$0.11M
Unnamed bot0x45e9…9215$3.24M$3.51M−$0.82M

Address labels mark 0xae2f…ae13 as jaredfromsubway, one of Ethereum's best-known MEV bots. It caught one of the biggest shares of the dumped tokens' discount, then paid even more than that to block builders as priority fees. It ended the night slightly down on these trades. A contract labelled as Wintermute's, the market-making firm in our Coinbase tokenized stocks piece, kept a small gain.

09 · RLUSDRLUSD broke for ten minutes

The hacker also sold 48 million RLUSD, Ripple's dollar token, over about twenty minutes that evening. The price slipped, and one trade printed as low as $0.81. Within minutes it was back near a dollar.

Five minutes from (UTC)CloseIn that bar
21:15$1.0037before the sale
21:45$0.9984selling starts
21:50$0.9867low $0.9476
21:55$0.9961low $0.9393; one trade at $0.81
22:00$0.9986back near a dollar

Because most of the sale filled close to a dollar, the hacker lost only $263K on it. Traders who bought the dip made $232K before costs. Our earlier look at RLUSD on the XRP Ledger covers the token's other home.

10 · Still at stakeWhat the hacker can still take out of Aave

Before the freezes, the hacker deposited 60 million USDT into Aave, a lending app, and borrowed ETH against it. Tether cannot freeze that USDT, because Aave holds it, and Aave's deposit freeze does not stop withdrawals. Our audit of Tether's blacklist explains how those freezes work.

What stops the hacker now is cash. Other lenders pulled their USDT out of Aave that night, and by the morning of 30 October Aave's USDT pool held only $4,707. A test withdrawal from the hacker's account to a fresh address works up to about $3,185. If lenders put USDT back, the hacker could take out up to $3.6M before its loan's safety limit stops it.

11 · The methodHow we measured it

We compared every trade with the price on Hyperliquid, a large crypto exchange, in the same minute. Dollar tokens count at one dollar. A trade above that price is the buyer's loss and the seller's gain. We added up each wallet's trades over the night, then took off what it paid in gas and in tips to block builders, counting each cost once.

Four separate ledgers cover the ETH buys, the TRON buys, the token dumps and the RLUSD sale. A separate checker rebuilt each one from different data and found errors we then fixed. The $4.5M we could not trace is mostly ETH bought through tokens we did not measure, and 21 small tokens whose discount we did not split. The trades come from Bitquery's Ethereum dataset.

Limits on these findings

Market prices come from Hyperliquid, minute by minute. For TRX and the dumped tokens these are futures prices, which can sit slightly above or below spot. Dollar tokens count at one dollar.

Ethereum trades are counted from 20:30 UTC on 29 October to 01:00 UTC on 30 October, when the pool gap had closed. TRON trades and token sales run to 07:00 UTC.

Wallets are the addresses that paid for each trade. One firm can use many wallets, so the counts of wallets overstate the number of firms.

Gains are measured at the price of each trade. Bots that bought their ETH or TRX elsewhere first had costs there that this does not include.

Names come from address labels and are given only for wallets that are both labelled and widely known by that name.

The Aave figures were read at 09:37 UTC on 30 October and change as lenders add or remove USDT.

12 · The recordThe addresses behind these findings

0x7aa4d3029e4c6a8e916300014ad95b6d6c03bfd1
0x77edef23fbd05921c26fe29fcc3a65e14d2ac3eb
0xe7024ab80143b1ef843efe6a58368696cb87958d
0x8d53903625b8e839b9df4bd28b0efb1cd6b8639a
0xbeef02961503351625926ea9a11ae13b29f5c555
0x0000000000be226afde21672a5e4adc45692e69d
0x9b1303ebf09bc51b7fac376c9e421e8daae63b82
0x0cdd9cbb825212c6cc5b0b36239e94218ee661d8
0x9008d19f58aabd9ed0d60971565aa8510560ab41
0xae2fc483527b8ef99eb5d9b44875f005ba1fae13
0x51c72848c68a965f66fa7a88855f9f7784502a7f
0xfeeeeee44046c3f61a8cc081e0918ef0de0a7ffc
0x388c818ca8b9251b393131c08a736a67ccb19297
0x90cbe4bdd538d6e9b379bff5fe72c3d67a521de5
TSUUVjysXV8YqHytSNjfkNXnnB49QDvZpx
TS5v9Z9frcc6zerQmUsLBCEp28fdabNZC7
TSpe5HC3PRD2svJcr1YoGszhHk2mtkyZ8A
TM8uyBjRKzFtQdMC7tQLvKeeWieaFvXDyc
Run it yourself

Ask who traded against a hacker, in plain English

Every trade in this story comes from Bitquery's blockchain data. The Bitquery MCP server puts that data behind an AI assistant, so you can ask which wallets traded a pool, what a wallet made, 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 TRON dataset.

See every trade in a pool, minute by minuteFind the wallets that made the most on a tokenCheck an address against Bitquery's labelsFollow a hacker's wallets on Ethereum and TRON
Explore Bitquery MCP →Trades, transfers 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, protocol or service.

The findings describe trades and transfers observed on Ethereum and TRON 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, Ripple, Ethena, Uniswap, 1inch, CoW Protocol, Compound, Aave, Lido, Titan, SunSwap, Hyperliquid, Wintermute, jaredfromsubway or any other named project, company, bot or service describe what the public record shows about addresses and transactions linked to them. They are not statements about any party's intent or conduct, and nothing here asserts that any named party acted unlawfully. Trading against a hacker's public orders is ordinary market activity.

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

Who profited from the Binance hack?

Traders and their bots made the most. While the hacker swapped stolen coins in a hurry, they sold to it at high prices and bought its tokens cheap, and kept about $60M after costs. Ethereum's block builders and validators took about $30M in tips and fees from the same bots.

How much did the Binance hacker lose by swapping?

About $119M against market prices. Most of it came from overpaying for ETH on Ethereum. The rest came from selling stolen tokens cheap, overpaying for TRX on TRON and a small loss on RLUSD.

What is an MEV bot?

An MEV bot is a trading program that hunts for price gaps and other chances to profit from the order of transactions in a block. MEV stands for maximal extractable value. Bots pay block builders to put their trades first.

What is a block builder?

A block builder is a firm that collects transactions and orders them into an Ethereum block. Bots pay builders tips to be placed first, and builders pay most of that on to the validator who adds the block to the chain.

Can the Binance hacker still withdraw money from Aave?

Only a little for now. The hacker's USDT deposit on Aave is still unfrozen. On the morning of 30 October, though, Aave's USDT pool was nearly empty, so a withdrawal worked only up to about $3,185. If lenders return, the hacker could withdraw up to $3.6M.

Why did ETH cost more on Uniswap during the Binance hack?

The hacker bought so much ETH so fast that it pushed up the price in the biggest Uniswap pools. ETH there rose to 38% above the rest of the market and stayed above it for hours while bots sold ETH back in.

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.