The bitcoin that Arkham attributes to the Bitget hacker has almost all left the wallets the analytics firm was watching. In a thread posted on X at 03:24 UTC on Tuesday 17 November, Arkham says 2,266.68 BTC went out of the wallets it labels “Bitget Hacker” in 11 days, mostly into mixers and CoinJoin transactions. It counts 34.63 BTC still sitting there, worth about $2.25 million by its own figures.
Arkham values the outflow at $161.04 million and writes that the hacker “has moved out almost the entirety of the original haul”. Its headline calls the movement laundering. What the thread documents is narrower than that word suggests: coins leaving a set of addresses that one company has tagged, and entering a tool built to break the trail.
Nobody else has confirmed the numbers. By 06:00 UTC on 17 November, some two and a half hours after the thread, Bitget had published nothing about it on its X account, and no other tracing firm had put out a count of its own for this November movement. The outlets that carried the figures overnight, PANews among them, cite Arkham alone. The text of the thread gives totals and time windows, without transaction identifiers or addresses that a reader could check on a block explorer.
What Arkham says left the Bitget hacker wallets
According to Arkham, the labelled wallets have sent out 206.06 BTC a day on average since 6 November. The busiest days it lists are 14 November, with 351.96 BTC, and 15 November, with 316.35 BTC. For 16 November the thread gives 77.07 BTC “so far”.
| Arkham’s count | BTC | Arkham’s dollar value |
|---|---|---|
| 12 November | 210.94 | $15.49M |
| 13 November | 234.38 | $16.18M |
| 14 November | 351.96 | $23.65M |
| 15 November | 316.35 | $20.27M |
| 16 November (partial day) | 77.07 | $4.99M |
| Total since 6 November | 2,266.68 | $161.04M |
| Of which into CoinJoin | 2,173.76 | $154.45M |
| Left in labelled wallets | 34.63 | $2.25M |
Almost all of it went the same way. Arkham puts the bitcoin sent into CoinJoin at 2,173.76 BTC, about 96% of the total: 2,065.43 BTC straight from the labelled wallets into what it calls WabiSabi CoinJoin rounds, and 108.33 BTC through new addresses first. WabiSabi is the protocol behind Wasabi Wallet’s coinjoins, which the wallet’s documentation describes as centrally coordinated: a coordinator server assembles each round.
For the last day, the thread gets more precise. It describes 55 BTC entering six CoinJoin rounds between 05:47 and 10:59 UTC on 16 November, then 21.35 BTC sent to new addresses in eight transactions between 12:28 and 15:27 UTC, plus 0.72 BTC in two earlier transactions.
The share going to mixing has grown. In its previous tally, posted on 11 November and reported by Blockonomi the next day, Arkham counted 1,052.34 BTC out in six days, 847.26 BTC of it (about 80%) in 66 CoinJoin transactions that began at 09:27 UTC on 6 November. At that point 959.29 BTC remained in the labelled wallets. Six days later the balance is down by 924.66 BTC.

$161 million at Arkham’s prices, about $147 million today
The dollar figure needs a caveat. Arkham’s $161.04 million works out to roughly $71,000 per bitcoin, and its daily lines imply a different price each day: about $73,400 for 12 November, $69,000 for 13 November, $64,700 for 16 November. Each transfer appears to be valued at the price of the day it happened, though the thread does not say so.
Bitcoin traded near $64,840 at 05:44 UTC on 17 November. At that price the same 2,266.68 BTC are worth about $147 million, and the 34.63 BTC left about $2.25 million. The gap comes from the price, which has fallen 12.7% in seven days, and not from the count.
What a CoinJoin does to a trail
Every bitcoin transaction is public. Anyone can follow coins from one address to the next, which is how Arkham and Bitget built their lists of the attacker’s addresses in the first place. A CoinJoin does not hide that. It is a single transaction in which many users put coins in together and take them out as new outputs, often of identical sizes, so that an outside observer cannot say which output belongs to which input.
The entry is visible: Arkham can see 2,173.76 BTC going in. The exit is the problem. After a round, each output could belong to any of the participants, and after several rounds the link back to a labelled wallet becomes a matter of probability, not proof. That is why Arkham’s count stops at the door of the mixer.
It matters for recovery because of how stolen bitcoin gets stopped in practice. Nobody can freeze bitcoin on the chain itself, as Tether or Circle can with their stablecoins. The usual chance comes later, when coins on a published list arrive at an exchange or a broker that checks deposits and blocks them. Mixed coins arrive without that history attached. Of the $387.5 million taken from Bitget, the amounts reported frozen in the weeks after the theft were around $1 million, mostly stablecoins.
Fresh addresses, and what the count leaves out
Leaving labelled wallets is not the same as being cashed out. Arkham’s thread lists 108.33 BTC that passed through new addresses before entering CoinJoin and another 21.35 BTC sent to new addresses on 16 November, and it does not say who controls them. The longer article it links to is titled “Bitget Hacker Moves Millions in BTC to New Wallets”. The Defiant, reporting on Arkham’s figures, adds that the 34.63 BTC is not a full accounting of everything the attacker may still control.
Arkham’s entity is one map among several. Bitget keeps its own, a public tracing dashboard with thousands of bitcoin addresses it ties to the attacker, and the two lists are not built the same way. When Arkham and Bitget’s tracker were compared on 11 November, they gave different CoinJoin totals for the same days (66 transactions and 847.26 BTC for Arkham, 72 transactions and 866.23 BTC of gross inputs for Bitget), and Bitget warns that its gross figure can count re-mixed coins twice.

Where the Bitget case stands
Bitget lost about $387.5 million from its hot and warm wallets on 24 September, a theft the exchange traces to a flaw in a third-party security product and says did not touch customer balances, which its protection fund covered. Coindaro’s account of the Bitget hack and the restart of withdrawals has the detail. The attacker swapped most of the loot into bitcoin, mainly through THORChain, and on 24 October Arkham still counted about 2,960 BTC in the labelled wallets.
That stock is now 34.63 BTC. Bitget’s chief executive, Gracy Chen, has pointed to North Korea, and Chainalysis, Elliptic and TRM Labs have each tied the theft to North Korea-linked actors with varying confidence. No law-enforcement agency had publicly confirmed that when Coindaro last updated its account of the hack on 24 October. The separate Binance theft is different: the FBI named North Korea’s TraderTraitor on 1 November.
Bitget’s bounty, as announced after the theft, is 5% of any funds frozen or recovered, run through Bybit’s LazarusBounty platform; freezes made under court orders or at the request of law enforcement do not qualify. Most thefts of this kind happen at the level of keys and servers, not of the chain, as our guide on where crypto hacks really happen explains, and the chain keeps the record afterwards. A label from Arkham or from Bitget on the fresh addresses, or mixed coins turning up at an exchange that screens deposits, would be the next checkable facts.
