Bitget Hacker Launders $161 Million in Bitcoin Through CoinJoin Mixers

Bitget Hacker Launders $161 Million in Bitcoin Through CoinJoin Mixers


Wallets belonging to the attacker behind Bitget’s September security incident have moved 2,266.68 BTC—valued at $161.04 million—out of tracked addresses over the preceding 11 days from November 17 2026, according to blockchain analytics firm Arkham. 

The bulk of these outflows entered CoinJoin transactions and newly created addresses, sharply reducing the visible balance remaining in the labelled cluster. The activity continues a multi-week process of dispersing proceeds from the original $387.5 million drain of the exchange’s hot and warm wallets. 

Attacker moved 2,266.68 BTC ($161M) in 11 days, funneling 2,173.76 BTC through CoinJoin mixers.

Daily outflows averaged 206 BTC, with peak 351.96 BTC on November 14, reducing labeled balance to 34.63 BTC.

Funds were routed via new addresses, WabiSabi CoinJoin, and earlier cross-chain bridges, complicating recovery.

The September Breach and Ongoing On-Chain Movements

On September 24, 2026, Bitget reportedly detected unauthorized transfers beginning at 18:31 UTC from portions of its hot and warm wallet infrastructure across multiple blockchains. The exchange’s official accounting later placed the affected total at approximately $387.5 million to $388 million. 

Bitget stated that private keys were not compromised and that cold wallets remained unaffected. Investigators determined that the attacker exploited a vulnerability in a third-party security product to obtain high-privilege internal credentials, then used those credentials to inject forged withdrawal commands that the exchange’s own systems signed. Independent forensic work by Mandiant and SlowMist supported this assessment of a supply-chain compromise that began weeks earlier.

Arkham’s onchain data show that the recent 11-day window produced consistent daily outflows averaging roughly 206 BTC. Specific recent daily totals included 210.94 BTC on November 12, 234.38 BTC on November 13, 351.96 BTC on November 14, 316.35 BTC on November 15, and 77.07 BTC on November 16. Of the 2,266.68 BTC that left the labelled wallets, 2,173.76 BTC ($154.45 million) entered CoinJoin rounds. 

The majority—2,065.43 BTC—moved directly into WabiSabi CoinJoin transactions, while 108.33 BTC passed through intermediate new addresses first. On November 16 alone, 55 BTC entered six separate CoinJoin rounds between 05:47 and 10:59 UTC, with additional amounts sent to fresh addresses later in the day. The labelled wallets now hold only 34.63 BTC, or about $2.25 million. These figures represent the balances in addresses Arkham has attributed to the attacker; other unlabelled wallets controlled by the same party may exist outside the current cluster.

Earlier phases of fund movement involved cross-chain bridges, decentralized exchanges, and privacy-focused tools. Tracking of those initial dispersion paths documented attempts to convert assets into Bitcoin and other instruments while law-enforcement and exchange freezes recovered only limited sums. 

Bitget has maintained a public fund tracer and offered bounties for information leading to freezes or recoveries. The exchange’s User Protection Fund, which held more than $464 million at the time of the incident, is covering user losses. Withdrawals were restored in phases and fully operational by October 2, 2026.

How Cryptocurrency Hackers Launder Stolen Funds

Attackers who obtain large sums of cryptocurrency typically seek to break the public link between the original theft addresses and the final destination of the funds. CoinJoin is one of the widely used techniques on Bitcoin. In a CoinJoin transaction, multiple participants contribute inputs and receive outputs in a single collaborative transaction. Because many inputs are combined and outputs are often of similar value, an outside observer cannot reliably determine which output corresponds to which input. 

The WabiSabi protocol used by Wasabi Wallet and related coordinators implements this process in a non-custodial manner: participants retain control of their keys throughout, and the coordinating server cannot steal funds or directly map inputs to outputs.

In the Bitget case, the rapid movement of the majority of the recent BTC outflows into CoinJoin rounds is consistent with an attempt to increase the anonymity set of the coins before they are spent or further converted. Additional common steps include routing through new, previously unused addresses (creating a longer hop chain), using cross-chain bridges or decentralized swap protocols like THORChain to change asset types, and eventually cashing out through over-the-counter desks, peer-to-peer trades, or exchanges that perform weaker compliance checks. 

Read: Coldcard Hacker Moves 45% of Wave 3 Bitcoin via THORChain and CoinJoins

Privacy coins and shielded pools on other networks have also appeared in related tracing. Each step raises the cost and complexity of continued forensic analysis, although blockchain data remains permanently public and can still be examined with clustering heuristics, timing analysis, and off-chain intelligence. 

These methods do not make funds untraceable; they increase the resources required to follow them. Law enforcement and analytics firms continue to monitor mixer outputs for subsequent patterns that may re-link the coins to known entities.

Remaining Holdings and Implications for Recovery

With only 34.613 BTC left in the currently labelled wallets, the visible portion of the original Bitcoin holdings attributable to the attacker has been almost entirely dispersed. Arkham’s entity page and associated transfer graphs illustrate the progressive decline from higher balances earlier in November. Recovery prospects now depend on identifying post-mix outputs that enter regulated venues, cooperate with freezing requests, or exhibit other behavioral links. 

Bitget has stated that it continues to work with authorities and on-chain security partners, and that no further unauthorized transfers from its own infrastructure have occurred since containment. 

The incident has reinforced attention on third-party software supply-chain risks and the operational security of hot-wallet signing systems. Bitget’s own post-incident measures included credential resets, strengthened verification steps, and an expanded User Protection Fund. 

For the broader industry, the scale of the original theft—one of the larger exchange incidents of 2026—and the subsequent use of established privacy tools illustrate both the speed with which large sums can be moved and the persistent challenges of asset recovery once funds leave the initial addresses. Ongoing public tracking by firms such as Arkham continues to provide real-time visibility into remaining labelled balances and new outflows.

Also read: Crypto-Draining iOS Malware Hits 178 Firms, Including Ledger, HSBC, Zoom via Optimizely


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.







Leave a Reply

Your email address will not be published. Required fields are marked *