0x340fc413340f…340fc416
Bitcoin Traces $388 Million Bitget Incident Through Unlabeled Wallets
Bitcoin records confirm five transfers from Bitget-linked wallets totaling 26.19 BTC. The spending trail shows continued movement, but not a confirmed exchange deposit, cash-out or recovery.

Outputs
Five Nov. 16 Bitcoin transactions had recipient outputs totaling about 26.19 BTC.
The first two payments, 8.892934 BTC and 5.2997487 BTC, were valued at roughly $908,000 combined and were later spent.
The two 5 BTC outputs and the 2 BTC output confirmed at about 7:59 a.m. ET; both 5 BTC outputs were spent, while the 2 BTC output remained unspent when checked.
One 5 BTC payment later became an input to a transaction with 193 inputs and hundreds of outputs.
Bitget put the final affected amount at approximately $388 million and said withdrawals were fully restored on Oct. 2.
By Daniel Okafor
Five Bitcoin transactions carried about 26.19 BTC in recipient payments from wallets Arkham linked to the Bitget attacker on Nov. 16, according to Arkham’s report and transaction records independently visible on Bitcoin; Bitget put the wider incident’s final affected amount at approximately $388 million.
The recipient outputs were approximately 8.89 BTC, 5.30 BTC, 5 BTC, 5 BTC and 2 BTC. Their combined size is not a separate estimate of the total funds stolen: some transactions combined inputs Arkham had labeled with others it had not labeled.
Where did the Bitcoin move?
The first two payments were confirmed in the same block at about 7:28 a.m. ET. Recipient amounts were 8.892934 BTC and 5.2997487 BTC, which Arkham valued at roughly $908,000 combined. Both outputs had been spent again by the time of the report.
The two 5 BTC payments and the 2 BTC payment were confirmed at about 7:59 a.m. ET. Both 5 BTC outputs were later spent, while the 2 BTC output remained unspent when checked for the report.
The timing establishes sequence on the public ledger, not the recipients’ identities or the purpose of the transfers. The spending data likewise shows that several outputs moved into later transactions without establishing whether any sale occurred.
One of the 5 BTC payments then became an input to a transaction with 193 inputs and hundreds of outputs. That establishes further movement, not a confirmed exchange deposit or cash-out. Arkham’s identification of CoinJoin activity is an attribution by the analytics firm, distinct from the amounts and spending history visible on Bitcoin itself.
Does the trail prove the attacker still controls the Bitcoin?
Arkham said continued attacker control was “the most likely explanation” for the unlabeled destinations, while acknowledging that some bitcoin could have changed hands through over-the-counter desks or laundering services. A transfer out of a known address therefore does not necessarily mean the attacker sold the coins or surrendered control.
Bitcoin itself does not record the counterparties’ identities. The link to the hack rests on address attribution: Arkham labels the originating wallets as belonging to the Bitget attacker. The source addresses for all five transactions also appear in the attacker-address API linked from Bitget’s official incident page, corroborating their connection to the exchange’s investigation.
The API match supports treating the addresses as part of the Bitget incident, not as an unrelated collection of wallets. It does not establish the identity or control of the recipients. Any conclusion that a recipient was an exchange, an OTC desk or a laundering service would require attribution beyond the raw transaction and spending records.
How large was the Bitget incident?
Bitget said in September that approximately $387.5 million had been transferred to attacker-controlled addresses. Its subsequent incident update put the final affected amount at approximately $388 million. The exchange said withdrawals were “fully restored on Oct. 2,” while fund tracking and recovery remained ongoing.
The 26.19 BTC examined here is therefore a set of traceable recipient outputs within a much larger incident, not an additional $388 million in affected funds. That distinction matters for loss estimates and recovery accounting because the underlying transactions combined both labeled and unlabeled inputs.
What should readers watch next?
The immediate test is whether the 2 BTC output still unspent at the report check changes hands, and whether any destination can be tied to an exchange, OTC desk or laundering service. Until that attribution appears, the transactions show movement from Bitget-linked wallets rather than monetization; Bitget said, “Fund tracking and recovery remain ongoing.”
via cryptonews.net (Source)
More from Daniel Okafor
Show full bio
Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.
1,514 articles