0x26154e752615…26154e72

ConfirmedSecurity467 vB111 sat/vB2 min decode

Bitget-Linked Addresses Push 847 BTC Into CoinJoin Mixers

Addresses tied to Bitget's Sept. 24 breach moved 1,052.34 BTC ($78.61M) in six days, sending 847.26 BTC into CoinJoin; 959.29 BTC worth $71.44M remains on-chain.

Bitget-Linked Addresses Move 847.26 Bitcoin (BTC) Into CoinJoin Over Six Days
WitnessBitget-Linked Addresses Move 847.26 Bitcoin (BTC) Into CoinJoin Over Six DaysWorldSpectrum / pixabay

Outputs

  1. Bitget-linked addresses moved 1,052.34 BTC (~$78.61M) over six days following the Sept. 24 incident.

  2. 847.26 BTC (~$63.43M) was sent into CoinJoin transactions during the same period.

  3. The addresses still held 959.29 BTC (~$71.44M) after the movements.

  4. Bitget revised its loss estimate from $351.6M to ~$387.5M after adding Zcash and TRON assets.

  5. An earlier trace showed ~4 BTC from the incident entering a Wasabi CoinJoin round.

Addresses tied to Bitget's Sept. 24 security incident moved 1,052.34 Bitcoin (BTC) — roughly $78.61 million — over six days, and 847.26 BTC of that, worth about $63.43 million, went into CoinJoin transactions, according to on-chain records.

The wallets still held 959.29 BTC, valued around $71.44 million, at the end of the tracking window. The movement marks a sustained, structured effort to break the transaction trail rather than a single dump.

What is CoinJoin and why does it matter here?

CoinJoin pools multiple users' Bitcoin inputs into one collaborative transaction, obscuring which output belongs to which sender. It's a privacy tool, not an exchange feature. Once coins enter a mixing round, following the path from the Bitget incident addresses becomes substantially harder for analysts, exchanges and law enforcement.

This wasn't the first mixing signal from the breach. An earlier trace showed roughly 4 BTC linked to the incident entering a Wasabi CoinJoin round. The new activity scales that pattern up by two orders of magnitude: 847.26 BTC across the six-day stretch, on-chain data shows.

For any recovery effort, each CoinJoin round raises the cost of attribution. Compliance teams at exchanges receiving downstream funds will face heuristics, not certainties, when screening deposits.

How big was the Bitget incident?

Bitget initially put the Sept. 24 incident at about $351.6 million. The exchange later revised the figure to roughly $387.5 million after accounting for assets held on Zcash and TRON in addition to the original inventory.

The revision itself is telling. The attacker's footprint spans at least three chains — Bitcoin, Zcash and TRON — which complicates any single-chain recovery or freeze strategy. Cross-chain movement is the standard playbook for laundering large hauls, and the revised number confirms the breach was broader than first reported.

What do the remaining balances mean?

The gap between the 1,052.34 BTC moved and the 959.29 BTC still sitting in linked addresses suggests the operation is mid-stream, not finished. If the same pattern holds, a meaningful share of the remaining $71.44 million could head into further mixing rounds or bridge to other chains.

Every figure here — the 847.26 BTC into CoinJoin, the $63.43 million mixed, the 959.29 BTC reserve — comes from on-chain tracing, the same method that surfaced the earlier 4 BTC Wasabi round.

The practical consequence for Bitget users is indirect but real: recovery of mixed funds typically depends on law enforcement action across jurisdictions, which runs on timelines of months or years, not exchange business days.

Expect continued wallet clustering around these addresses as tracing firms and exchanges update their screening lists — and watch whether the remaining 959.29 BTC moves into mixing or pivots toward liquidity venues instead.

via tokenpost.com (Source)

More from Daniel Okafor

Daniel Okafor

Show full bio

Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.

1,011 articles