Figures as of 2026-09-12 08:30:28 UTC · block 966,642 · updated once a day
Still unmovedIt depends entirely on where your share of the money went. There are five possible answers, and they are very different. The chart below shows how much of the stolen total is in each.
Five days of theft, then almost nothing. Every figure below is read from the Bitcoin blockchain.
Prefer the story to the balances? Read the full investigation — the narrative account of how the exploit worked and how the money was moved. Its figures are frozen at 7 August 2026 and cover a narrower address set than this page, which keeps updating.
The theft starts. In about 40 minutes 1,196 wallets are emptied of 1,082.65 BTC. Most had been sitting untouched for years — the typical victim wallet had not moved in over three years.
Three more waves follow. By the 3rd the total reaches 1,789.28 BTC across 8,865 wallets — worth about $114.7M at the prices of the day.
The thieves try the exits. Roughly 7.46 BTC reaches Unnamed high-volume service, ChangeNow, KuCoin, Quidax and other services. That is 0.4% of everything taken — a rounding error against the pile. Another 136.21 BTC goes through CoinJoin mixers instead.
30.18 BTC is shuffled out of one collecting address into a fresh one. It has sat there ever since.
1.05 BTC leaves one of the parked addresses and is run through a CoinJoin mixer the next day — the only attempt at covering tracks in weeks, and a trivial sum against what is still sitting still.
1,332.34 BTC — about $103.4M — has never been spent. Nothing has reached an exchange for 39 days. The single largest pile, 562.02 BTC ($43.6M), has never been touched at all.
20.69 BTC is walked through a chain of fresh addresses and swapped to ether through THORChain, a swap protocol with no operator to freeze anything. The ether lands at one Ethereum address, which we now watch alongside the bitcoin.
Follow the ribbons left to right: from the victims, into the thieves’ collection addresses, to where each coin sits today. Widths are proportional to BTC.
Every time traced coins landed somewhere a freeze is possible. If you are a victim, these are the transaction IDs to put in your police report and to quote when you contact the exchange. Each links to the block explorer so anyone can verify it independently.
| Date | Service | Traced to this theft | Transaction | |
|---|---|---|---|---|
| 2026-08-04 |
Unnamed high-volume service
bc1q2nfxrvvg67nhey0gk0… |
2.00 BTC
$155,200 of 2.00 BTC moved in this transaction |
927183853a12d34241fb61bbfb… | |
|
How the money got there — 1 transaction, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-04 · this transaction moved 2.00 BTC ·
927183853a12d34241fb61…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 2.00 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-04 |
Unnamed high-volume service
bc1q2nfxrvvg67nhey0gk0… |
2.00 BTC
$155,200 of 2.00 BTC moved in this transaction |
1a454301c7f9cb41193b63e82d… | |
|
How the money got there — 1 transaction, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-04 · this transaction moved 2.00 BTC ·
1a454301c7f9cb41193b63…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 2.00 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-04 |
Unnamed high-volume service
bc1qqa7p9qj89f6vg3yhue… |
1.00 BTC
$77,607 of 1.00 BTC moved in this transaction |
2c7075a3388b88c29d976d8629… | |
|
How the money got there — 1 transaction, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-04 · this transaction moved 1.00 BTC ·
2c7075a3388b88c29d976d…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 1.00 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-04 |
Unnamed high-volume service
bc1qqa7p9qj89f6vg3yhue… |
1.00 BTC
$77,607 of 1.00 BTC moved in this transaction |
064eb61de80cff3e74408a99de… | |
|
How the money got there — 1 transaction, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-04 · this transaction moved 1.00 BTC ·
064eb61de80cff3e74408a…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 1.00 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-02 |
ChangeNow
3KMmeqPeQcngyTehdfSwsG… reached it after 2 hops |
0.45 BTC
$34,917 of 0.45 BTC moved in this transaction |
3cf126caaa9b119537df7cce86… | |
|
How the money got there — 3 transactions, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-02 · this transaction moved 0.45 BTC ·
5ecc3052f5ce02dcc39f1a…
2
2026-08-02 · this transaction moved 0.45 BTC ·
a7bf30f03b5ffd33f671b4…
3
2026-08-02 · this transaction moved 0.45 BTC ·
3cf126caaa9b119537df7c…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 0.45 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-02 |
ChangeNow
3KMmeqPeQcngyTehdfSwsG… reached it after 4 hops |
0.27 BTC
$20,703 of 0.45 BTC moved in this transaction |
3cf126caaa9b119537df7cce86… | |
|
How the money got there — 5 transactions, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-01 · this transaction moved 0.41 BTC ·
e4aeb758da01c9ded47589…
2
2026-08-01 · this transaction moved 0.50 BTC ·
ad2c9a4d2f20255729852d…
3
2026-08-02 · this transaction moved 0.45 BTC ·
5ecc3052f5ce02dcc39f1a…
4
2026-08-02 · this transaction moved 0.45 BTC ·
a7bf30f03b5ffd33f671b4…
5
2026-08-02 · this transaction moved 0.45 BTC ·
3cf126caaa9b119537df7c…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 0.27 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-02 |
ChangeNow
3KMmeqPeQcngyTehdfSwsG… reached it after 2 hops |
0.24 BTC
$18,727 of 0.55 BTC moved in this transaction |
d0bcdc4a7306256b5cab1ec086… | |
|
How the money got there — 3 transactions, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-02 · this transaction moved 0.24 BTC ·
5ecc3052f5ce02dcc39f1a…
2
2026-08-02 · this transaction moved 0.24 BTC ·
135d4c2cb95a908572f15f…
3
2026-08-02 · this transaction moved 0.55 BTC ·
d0bcdc4a7306256b5cab1e…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 0.24 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-02 |
ChangeNow
3KMmeqPeQcngyTehdfSwsG… reached it after 4 hops |
0.14 BTC
$11,104 of 0.55 BTC moved in this transaction |
d0bcdc4a7306256b5cab1ec086… | |
|
How the money got there — 5 transactions, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-01 · this transaction moved 0.41 BTC ·
e4aeb758da01c9ded47589…
2
2026-08-01 · this transaction moved 0.50 BTC ·
ad2c9a4d2f20255729852d…
3
2026-08-02 · this transaction moved 0.24 BTC ·
5ecc3052f5ce02dcc39f1a…
4
2026-08-02 · this transaction moved 0.24 BTC ·
135d4c2cb95a908572f15f…
5
2026-08-02 · this transaction moved 0.55 BTC ·
d0bcdc4a7306256b5cab1e…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 0.14 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-03 |
KuCoin
bc1q9wvygkq7h9xgcp59mc… reached it after 6 hops |
0.09 BTC
$6,918 of 1.61 BTC moved in this transaction |
dca71d9699814ce27912170a7e… | |
|
How the money got there — 7 transactions, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-02 · this transaction moved 0.51 BTC ·
ff327937e653fc40b34e35…
2
2026-08-02 · this transaction moved 0.27 BTC ·
61c0ddac816958a5a6b581…
3
2026-08-02 · this transaction moved 0.27 BTC ·
f37419c0bfd305402085ef…
4
2026-08-03 · this transaction moved 1.54 BTC ·
36e9dc53b7b3f91944c483…
5
2026-08-03 · this transaction moved 0.84 BTC ·
977dd39f4dbddb51cfcfc3…
6
2026-08-03 · this transaction moved 0.84 BTC ·
e205f1f4c51f31ca23d181…
7
2026-08-03 · this transaction moved 1.61 BTC ·
dca71d9699814ce2791217…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 0.09 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-03 |
KuCoin
bc1q9wvygkq7h9xgcp59mc… reached it after 5 hops |
0.07 BTC
$5,776 of 0.81 BTC moved in this transaction |
0b1e5e1954499c497c872cf003… | |
|
How the money got there — 6 transactions, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-02 · this transaction moved 0.51 BTC ·
ff327937e653fc40b34e35…
2
2026-08-02 · this transaction moved 0.27 BTC ·
61c0ddac816958a5a6b581…
3
2026-08-02 · this transaction moved 0.27 BTC ·
f37419c0bfd305402085ef…
4
2026-08-03 · this transaction moved 1.54 BTC ·
36e9dc53b7b3f91944c483…
5
2026-08-03 · this transaction moved 0.70 BTC ·
977dd39f4dbddb51cfcfc3…
6
2026-08-03 · this transaction moved 0.81 BTC ·
0b1e5e1954499c497c872c…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 0.07 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-02 |
ChangeNow
3KMmeqPeQcngyTehdfSwsG… reached it after 2 hops |
0.06 BTC
$4,683 of 0.35 BTC moved in this transaction |
901df57e6215b7d7ec2197b4cf… | |
|
How the money got there — 3 transactions, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-01 · this transaction moved 0.06 BTC ·
24f4b236bc47fc2ad85287…
2
2026-08-02 · this transaction moved 0.27 BTC ·
5d5a76bae994787135e035…
3
2026-08-02 · this transaction moved 0.35 BTC ·
901df57e6215b7d7ec2197…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 0.06 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-03 |
KuCoin
bc1q9wvygkq7h9xgcp59mc… reached it after 6 hops |
0.06 BTC
$4,466 of 1.61 BTC moved in this transaction |
dca71d9699814ce27912170a7e… | |
|
How the money got there — 7 transactions, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-02 · this transaction moved 0.51 BTC ·
ff327937e653fc40b34e35…
2
2026-08-02 · this transaction moved 0.27 BTC ·
61c0ddac816958a5a6b581…
3
2026-08-02 · this transaction moved 0.27 BTC ·
f37419c0bfd305402085ef…
4
2026-08-03 · this transaction moved 1.54 BTC ·
36e9dc53b7b3f91944c483…
5
2026-08-03 · this transaction moved 0.84 BTC ·
977dd39f4dbddb51cfcfc3…
6
2026-08-03 · this transaction moved 0.84 BTC ·
e205f1f4c51f31ca23d181…
7
2026-08-03 · this transaction moved 1.61 BTC ·
dca71d9699814ce2791217…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 0.06 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-03 |
KuCoin
bc1q9wvygkq7h9xgcp59mc… reached it after 5 hops |
0.05 BTC
$3,729 of 0.81 BTC moved in this transaction |
0b1e5e1954499c497c872cf003… | |
|
How the money got there — 6 transactions, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-02 · this transaction moved 0.51 BTC ·
ff327937e653fc40b34e35…
2
2026-08-02 · this transaction moved 0.27 BTC ·
61c0ddac816958a5a6b581…
3
2026-08-02 · this transaction moved 0.27 BTC ·
f37419c0bfd305402085ef…
4
2026-08-03 · this transaction moved 1.54 BTC ·
36e9dc53b7b3f91944c483…
5
2026-08-03 · this transaction moved 0.70 BTC ·
977dd39f4dbddb51cfcfc3…
6
2026-08-03 · this transaction moved 0.81 BTC ·
0b1e5e1954499c497c872c…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 0.05 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-07 |
Quidax
bc1qcgjnpnsnsyklteqmsu… reached it after 3 hops |
0.02 BTC
$1,803 of 1.01 BTC moved in this transaction |
78c7235897b8bfeb67e7373bee… | |
|
How the money got there — 4 transactions, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-08 · this transaction moved 0.00 BTC ·
cd1d56832574a47017bd31…
2
2026-08-05 · this transaction moved 0.03 BTC ·
24ee02cf811911764953ac…
3
2026-08-07 · this transaction moved 0.02 BTC ·
55af9e8d8e79543aae5dcc…
4
2026-08-07 · this transaction moved 1.01 BTC ·
78c7235897b8bfeb67e737…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 0.02 BTC of what finally arrived traces back to this theft.
| ||||
| 2026-08-04 |
Unnamed high-volume service
bc1qqa7p9qj89f6vg3yhue… |
0.01 BTC
$790 of 0.01 BTC moved in this transaction |
780ea04371adee7490a2409484… | |
|
How the money got there — 1 transaction, oldest first. Each line is a real transaction you can open and verify.
1
2026-08-04 · this transaction moved 0.01 BTC ·
780ea04371adee7490a240…
Amounts change between steps because the thief’s coins are mixed with other people’s money at each hop. Only 0.01 BTC of what finally arrived traces back to this theft.
| ||||
2 further movements are deliberately not listed here. They reached services too, but the addresses they came from were funded only by wallets that predate the exploit, and the amounts passed through unchanged — the signature of an owner moving their own coins to safety after the news broke, not a thief cashing out. Calling those a cash-out would smear both a victim and an exchange, so we leave them out until they can be resolved.
20.69 BTC of the traced coins was converted to ether through THORChain in 36 swaps, landing at the Ethereum address 0x160a7A4c067B084F03400c6980Ac29F73F6782f6 — which holds 0 ETH as of 2026-09-12 06:37 UTC. Each Bitcoin transaction below carries THORChain's own memo naming that destination, so the link is the protocol's, not our inference. No exchange holds these coins.
| Date | Traced to this theft | Destination chain · address | Protocol memo | Bitcoin transaction |
|---|---|---|---|---|
| 2026-08-02 | 0.15 BTC of 0.24 in the transaction |
ETH · 0x6A08B5B2…C0df06 | =:e:0x6A08B5B20F23FcFE09f5da… | 936c5f7d8539… |
| 2026-08-02 | 0.09 BTC of 0.24 in the transaction |
ETH · 0x6A08B5B2…C0df06 | =:e:0x6A08B5B20F23FcFE09f5da… | 936c5f7d8539… |
| 2026-09-02 | 0.40 BTC of 0.40 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 2e20a8e8d1ca… |
| 2026-09-02 | 1.42 BTC of 10.00 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 2dbea8817f2c… |
| 2026-09-02 | 0.98 BTC of 10.10 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | b24e76662345… |
| 2026-09-02 | 7.05 BTC of 8.58 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 387ca0e9c6e4… |
| 2026-09-03 | 2.50 BTC of 10.64 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | bb8d8a441438… |
| 2026-09-03 | 0.42 BTC of 10.64 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | bb8d8a441438… |
| 2026-09-03 | 0.86 BTC of 2.00 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 61f26287a53c… |
| 2026-09-03 | 0.86 BTC of 2.00 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 61f26287a53c… |
| 2026-09-03 | 0.14 BTC of 2.00 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 61f26287a53c… |
| 2026-09-03 | 0.14 BTC of 2.00 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 61f26287a53c… |
| 2026-09-03 | 1.07 BTC of 3.72 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | c7da47f55cb4… |
| 2026-09-03 | 0.92 BTC of 3.72 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | c7da47f55cb4… |
| 2026-09-03 | 0.53 BTC of 3.72 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | c7da47f55cb4… |
| 2026-09-03 | 0.53 BTC of 3.72 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | c7da47f55cb4… |
| 2026-09-03 | 0.18 BTC of 3.72 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | c7da47f55cb4… |
| 2026-09-03 | 0.15 BTC of 3.72 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | c7da47f55cb4… |
| 2026-09-03 | 0.09 BTC of 3.72 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | c7da47f55cb4… |
| 2026-09-03 | 0.09 BTC of 3.72 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | c7da47f55cb4… |
| 2026-09-03 | 0.54 BTC of 2.00 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 678b94f40717… |
| 2026-09-03 | 0.46 BTC of 2.00 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 678b94f40717… |
| 2026-09-03 | 0.27 BTC of 2.00 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 678b94f40717… |
| 2026-09-03 | 0.27 BTC of 2.00 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 678b94f40717… |
| 2026-09-03 | 0.09 BTC of 2.00 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 678b94f40717… |
| 2026-09-03 | 0.08 BTC of 2.00 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 678b94f40717… |
| 2026-09-03 | 0.05 BTC of 2.00 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 678b94f40717… |
| 2026-09-03 | 0.05 BTC of 2.00 in the transaction |
ETH · 0x160a7A4c…6782f6 | =:e:0x160a7A4c067B084F03400c… | 678b94f40717… |
| 2026-09-03 | 0.06 BTC of 0.35 in the transaction |
ETH · 0x8B5b6500…e3D200 | =:e:0x8B5b650067841ff3bF28fF… | e7e1a3c6f731… |
| 2026-09-03 | 0.05 BTC of 0.35 in the transaction |
ETH · 0x8B5b6500…e3D200 | =:e:0x8B5b650067841ff3bF28fF… | e7e1a3c6f731… |
| 2026-09-03 | 0.04 BTC of 0.35 in the transaction |
ETH · 0x8B5b6500…e3D200 | =:e:0x8B5b650067841ff3bF28fF… | e7e1a3c6f731… |
| 2026-09-03 | 0.04 BTC of 0.35 in the transaction |
ETH · 0x8B5b6500…e3D200 | =:e:0x8B5b650067841ff3bF28fF… | e7e1a3c6f731… |
| 2026-09-03 | 0.03 BTC of 0.35 in the transaction |
ETH · 0x8B5b6500…e3D200 | =:e:0x8B5b650067841ff3bF28fF… | e7e1a3c6f731… |
| 2026-09-03 | 0.03 BTC of 0.35 in the transaction |
ETH · 0x8B5b6500…e3D200 | =:e:0x8B5b650067841ff3bF28fF… | e7e1a3c6f731… |
| 2026-09-03 | 0.02 BTC of 0.35 in the transaction |
ETH · 0x8B5b6500…e3D200 | =:e:0x8B5b650067841ff3bF28fF… | e7e1a3c6f731… |
| 2026-09-03 | 0.02 BTC of 0.35 in the transaction |
ETH · 0x8B5b6500…e3D200 | =:e:0x8B5b650067841ff3bF28fF… | e7e1a3c6f731… |
On Ethereum since then: 649 ETH in 73 transactions to TornadoCash eth 0x47CE0C6e…, 5 ETH in 1 transaction to 0x9dD14d97…, 0.48 ETH in 1 transaction to 0x8d0079D0… (0 ETH left, checked 2026-09-12 06:37 UTC). 649 ETH went into Tornado Cash, a mixer on Ethereum, which is the same dead end as a CoinJoin on Bitcoin: realistically gone.
| Time (UTC) | Amount | To | Transaction |
|---|---|---|---|
| 2026-09-04 09:22:47 | 0.4803 ETH | 0x8d0079D0…49C517 | 0x28297ff86b… |
| 2026-09-04 09:14:35 | 1 ETH | 0x47CE0C6e…3c2936 TornadoCash_eth | 0x8f58b077e2… |
| 2026-09-04 09:10:59 | 1 ETH | 0x47CE0C6e…3c2936 TornadoCash_eth | 0x21039bdf31… |
| 2026-09-04 09:09:47 | 1 ETH | 0x47CE0C6e…3c2936 TornadoCash_eth | 0x08774f8139… |
| 2026-09-04 09:08:47 | 1 ETH | 0x47CE0C6e…3c2936 TornadoCash_eth | 0x5ea5ee753b… |
| 2026-09-04 09:07:11 | 1 ETH | 0x47CE0C6e…3c2936 TornadoCash_eth | 0x91a603735e… |
| 2026-09-04 09:06:11 | 1 ETH | 0x47CE0C6e…3c2936 TornadoCash_eth | 0xef22a14b26… |
| 2026-09-04 09:04:47 | 1 ETH | 0x47CE0C6e…3c2936 TornadoCash_eth | 0x7dfd35bb64… |
| 2026-09-04 09:03:23 | 1 ETH | 0x47CE0C6e…3c2936 TornadoCash_eth | 0xbe28e36f94… |
| 2026-09-04 09:01:47 | 1 ETH | 0x47CE0C6e…3c2936 TornadoCash_eth | 0x9af10cbcf3… |
| 2026-09-03 19:45:35 | 10 ETH | 0x910Cbd52…b39DbF TornadoCash_eth | 0x216a8d8132… |
| 2026-09-03 19:44:11 | 10 ETH | 0x910Cbd52…b39DbF TornadoCash_eth | 0x8454436568… |
Read the two amounts carefully. A transaction often moves other people’s money in the same batch. We show what the whole transaction moved and how much of it traces back to this theft — only the second number is the thief’s, and claiming the first would be wrong.
Newest first. Tiny amounts sent to these addresses are ignored — strangers spam famous wallets with dust, and that is not the thief moving anything.
| When | How much | What happened |
|---|---|---|
| 7 Sep
5 days ago |
54.78 BTC
$4.3M |
Went into a CoinJoin mixing round, where it was combined with hundreds of other people's coins. The trail cannot be followed past this point.
block 965,854 · to bc1qpgwa8pn4mkew07… |
| 6 Sep
6 days ago |
54.78 BTC
$4.3M |
9 parked addresses were swept into one. The pile was moved on again shortly after.
block 965,850 · to bc1p7xunc8vxs9g3z3… |
| 5 Sep
7 days ago |
15.48 BTC
$1.2M |
Went into a CoinJoin mixing round, where it was combined with hundreds of other people's coins. The trail cannot be followed past this point.
block 965,632 · to bc1q44fwrxnp0nm9vx… |
| 5 Sep
7 days ago |
15.48 BTC
$1.2M |
Moved into a fresh address, which has since been emptied again.
block 965,625 · to bc1pacpd74fkvvxelc… |
| 3 Sep
9 days ago |
0.17 BTC
$13,290 |
Paid into a THORChain vault and swapped to ether. The protocol memo on the transaction names the Ethereum address that received it; nothing can be frozen on the Bitcoin side.
block 965,317 · to bc1qeay5x2ap5cycqg… |
| 3 Sep
9 days ago |
0.13 BTC
$9,897 |
From a holding address one step removed from the theft. Moved into a fresh address, which has since been emptied again.
block 965,316 · to bc1qvkx4ums4w4drpl… |
| 3 Sep
9 days ago |
4.00 BTC
$310,372 |
Paid into a THORChain vault and swapped to ether. The protocol memo on the transaction names the Ethereum address that received it; nothing can be frozen on the Bitcoin side.
block 965,307 · to bc1qeay5x2ap5cycqg… |
| 3 Sep
9 days ago |
5.72 BTC
$444,119 |
From a holding address one step removed from the theft. Moved into a fresh address, which has since been emptied again.
block 965,307 · to bc1q96me22q4mehpec… |
| 3 Sep
9 days ago |
7.72 BTC
$599,309 |
From a holding address one step removed from the theft. Moved into a fresh address, which has since been emptied again.
block 965,306 · to bc1qgw8v0fa7877ntr… |
| 3 Sep
9 days ago |
10.64 BTC
$825,972 |
Paid into a THORChain vault and swapped to ether. The protocol memo on the transaction names the Ethereum address that received it; nothing can be frozen on the Bitcoin side.
block 965,297 · to bc1qeay5x2ap5cycqg… |
| 3 Sep
9 days ago |
10.64 BTC
$825,973 |
From a holding address one step removed from the theft. Moved into a fresh address, which has since been emptied again.
block 965,295 · to bc1qgw8v0fa7877ntr… |
| 3 Sep
9 days ago |
1.53 BTC
$118,588 |
From a holding address one step removed from the theft. Moved into a fresh address, which has since been emptied again.
block 965,237 · to bc1qt8rrtnxlszm7rc… |
Every service the traced coins have reached. These are the places where a freeze is possible — if you are a victim, these names belong in your police report.
Which company an address belongs to comes from industry screening data. The behaviour beside each name — transaction counts, lifetime volume, the deposit itself — is measured by us directly from the blockchain, and you can verify every figure through the linked explorer.
| Service | Received (traced) | What it means for recovery |
|---|---|---|
| Unnamed high-volume service | 6.01 BTC $466,402 |
|
| ChangeNow | 1.16 BTC $90,133 |
Instant-swap service, no accounts. Freezes only if caught mid-swap — usually converted and gone within minutes.
Identity from industry screening data. Our own on-chain measurement of the receiving wallet: 282,026 transactions, 24,182 BTC lifetime volume. |
| KuCoin | 0.27 BTC $20,890 |
Offshore exchange. Has complied with freeze requests; slower path.
Identity from industry screening data. Our own on-chain measurement of the receiving wallet: 165,108 transactions, 333,505 BTC lifetime volume. |
| Quidax | 0.02 BTC $1,803 |
Identity from industry screening data. Our own on-chain measurement of the receiving wallet: 4,134 transactions, 569 BTC lifetime volume. |
6 confirmed · 17 traced · 2 attributed · 2 under review · 3 venue · 97 reported
Every address links to the Bitquery explorer so you can verify the balance yourself.
| Tier | Address | Balance BTC | UTXOs spent |
|---|---|---|---|
| CONFIRMED | bc1qq85v2c926eg6pgxhwp6q7lf6cnsz80qs3fcu9r independently corroborated as this exploit |
562.02148293 | none, ever |
| CONFIRMED | bc1qx76cae2706qd5q576feh7xq8rfcsjpf2htfhe3 independently corroborated as this exploit |
398.47576957 | none, ever |
| CONFIRMED | bc1q8jy96fe5lf8vfugydnte3cguk92gpev7kwtp3q independently corroborated as this exploit |
89.62329890 | none, ever |
| CONFIRMED | bc1qtfrwa4j6rmj9rsgspv6a0yjumkg39js2numu75 independently corroborated as this exploit |
45.90254994 | none, ever |
| CONFIRMED | bc1qnk4zh9qcnap2mycp56qjrgza3cc8ylrh8fecp0 independently corroborated as this exploit |
32.45061090 | 341 |
| CONFIRMED | bc1qmd5m5ktv7m5ffujxv4248fxv36myvdx79n8jp6 independently corroborated as this exploit |
0.00002000 | 93 |
| TRACED | bc1qez89sph5tgghmf36u79hq62h8n2xqqka05dt6n purpose-made: 2 txs, reached from a confirmed address |
30.18461929 only 30.18 traced to this theft |
none, ever |
| TRACED | bc1prjnvz77lhd3t6kdxt34x4yzgwu4qfdgyges8h6qhwldj60z5mcqs7pprpr purpose-made: 1 tx, reached from a confirmed address |
4.43713316 | none, ever |
| TRACED | bc1pynd6vswmxkghw6k5463xwcj7el7u4tpl2t2pnh0s8llmc2wgzfqsdu7h92 purpose-made: 2 txs, reached from a confirmed address |
0.00000000 | 1 |
| TRACED | bc1p7xunc8vxs9g3z3kv7yqkjsza9aephe5m73ynwdqg78m9kj0va3qq6akw44 purpose-made: 2 txs, reached from a confirmed address |
0.00000000 | 1 |
| TRACED | bc1qt8rrtnxlszm7rcdjpeepzk076jd5hevakqerzjyxpk8u3p6dfh2q92ua36 purpose-made: 6 txs, reached from a confirmed address |
0.00000000 | 3 |
| TRACED | bc1pacpd74fkvvxelcqtrc9zy8aevxlrvwj2mfe3wv9tn8a4jfmfyraqvekg6w purpose-made: 2 txs, reached from a confirmed address |
0.00000000 | 1 |
| TRACED | 334iKwmhLKzJFoijrcQwcBFfFth7QjJ6gB purpose-made: 2 txs, reached from a confirmed address |
0.00000000 | 1 |
| TRACED | bc1pynh7jn4jqh7h5v4l6fxxkjk7a0tqvt603ysnyn00824qmh2njcesd7ngxm purpose-made: 2 txs, reached from a confirmed address |
0.00000000 | 1 |
| TRACED | bc1qu2uq40wq04gmtjk09vcgv2dzxec4gsr25z6srw purpose-made: 4 txs, reached from a confirmed address |
0.00000000 | 2 |
| TRACED | bc1qsd9tklcz7yw72aztnlyfmn9hlc02tjq7ekjah8 purpose-made: 2 txs, reached from a confirmed address |
0.00000000 | 1 |
| TRACED | bc1qsgmet7sm4kvynn2ug6023v8j5tus2he76ly0yw purpose-made: 4 txs, reached from a confirmed address |
0.00000000 | 2 |
| TRACED | bc1qvrpckutek504fr8jv06hljxfslpw4cwf60cddc purpose-made: 2 txs, reached from a confirmed address |
0.00000000 | 1 |
| TRACED | bc1qw79velar2c0elc268fzxxn6ehe6v6n8lg683ha purpose-made: 2 txs, reached from a confirmed address |
0.00000000 | 1 |
| TRACED | bc1qlryk6u4f89r89qqp99rm4k6u8hr7tmyff79edm purpose-made: 2 txs, reached from a confirmed address |
0.00000000 | 1 |
| TRACED | bc1q72k76q3f4e068u63cja578nnvk87xc90wlaamt purpose-made: 20 txs, reached from a confirmed address |
0.00000000 | 10 |
| TRACED | bc1qpgr3806jwr98fdz07jqgvequkzemd7wrrpvd8e purpose-made: 2 txs, reached from a confirmed address |
0.00000000 | 1 |
| TRACED | bc1qa2xvdaflu9fcxg85e5varxe9t8g3yxe7z4c3y9 purpose-made: 2 txs, reached from a confirmed address |
0.00000000 | 1 |
| ATTRIBUTED | 3CTpBmp8uWTcHJBjmyVe8VPPyCHTzj2hBH Bullish - 4,889 txs, consistent with an exchange |
230.78528800 only 0.00 traced to this theft |
2435 |
Confirmed means an independent source ties the address to this exploit. Attributed means a named entity whose on-chain activity matches that claim. Traced means we reached it from a confirmed address. Venue means a high-volume service the money passed through — the address is not the holder’s own and its balance is not stolen money. Reported means published by other researchers and not yet reproduced by us. Nothing is called attacker-controlled on our word alone.
8,865 wallets were drained. The typical victim lost 0.0152 BTC (about $1,179), and the typical wallet had been sitting untouched for over three years — long-term savings, not trading money.
| Largest single losses | BTC taken | Wallet had been untouched since |
|---|---|---|
| bc1qxz7s2u6ful4cfm9daq7zwme579cpm9h2gqgf24 | 51.07 BTC $4.0M |
2025-08-03 |
| bc1qhrgyedsemlfnfcavlm0e6m5chzreczrew57uvw | 49.79 BTC $3.9M |
2025-08-03 |
| bc1qqzw7sl9fwx536u6u8aanzudl5xwstsw3ch4vmw | 30.00 BTC $2.3M |
2026-07-24 |
| bc1qe85jr4em79p66fsszkvfhwjf6p6qst58a2ahlr | 29.89 BTC $2.3M |
2025-07-18 |
| bc1qvshd3nv6mjjs5wtk6x5ekppakdp2trqcsdvwlf | 24.08 BTC $1.9M |
2024-01-30 |
| bc1qws3u2kw20y8q9k6sqe2p4k3whmrlawgft7qv47 | 17.39 BTC $1.3M |
2022-06-24 |
| bc1q928aamjwtgc5mfgrc348gryl7s7juhrst4344p | 17.25 BTC $1.3M |
2021-04-10 |
| bc1q30363smzw6uk5n2znj65mf9432s0e3d92e3fu5 | 14.43 BTC $1.1M |
2021-09-04 |
| bc1q9qaljdxux9nr4uuyh8v7khvk7hgvpku5e0xyjj | 14.25 BTC $1.1M |
2024-07-17 |
| bc1qgzxfgqgvnle9p6kksk35t54ycu2tx2hwau5ppw | 11.74 BTC $910,790 |
2024-03-07 |
The complete list of every wallet we traced is available as a spreadsheet further down, for researchers, exchanges and law enforcement. If you are a victim, you do not need it — check your own address privately below, and treat anyone who contacts you about your loss as a scammer until proven otherwise.
Everything on this page as spreadsheets, regenerated on every update. Open directly in Excel. Each file carries its own provenance header and the block it was compiled at.
If you run an exchange or a compliance desk: the attacker file is the one to screen deposits against. Read the classification column first — several rows are exchanges the funds passed through and must not be treated as attacker-controlled.
Paste a Bitcoin address to see whether it appears in the victim set we derived on-chain.
Derived independently by walking back from the attacker addresses: 4,718 victim addresses holding 1,479.00 BTC. That accounts for 99.51% of everything our watched addresses took in, but only 53.2% of the addresses Galaxy Research counts — we do not cover the whole theft, and we would rather say so than imply otherwise.