View post on X
The distinction matters for tracking the stolen money: a transfer out of a known address does not necessarily mean the attacker has sold the coins or surrendered control. In its research report, Arkham said continued attacker control was the most likely explanation for the unlabelled destinations, while acknowledging that some bitcoin could have changed hands through over-the-counter desks or laundering services.
What the Bitcoin Records Show
Bitcoin records independently confirm five transactions cited in Arkham’s report with recipient payments of approximately 8.89 $BTC, 5.30 $BTC, 5 $BTC, 5 $BTC and 2 $BTC on Nov. 16. Those recipient outputs total about 26.19 $BTC; they are not a separate estimate of net stolen funds, because some transactions combined inputs that Arkham labelled with others it had not labelled.
The first two payments were confirmed in the same block at about 7:28 a.m. ET. Their exact recipient amounts were 8.892934 $BTC and 5.2997487 $BTC, together worth roughly $908,000 using Arkham’s transaction valuations. Both recipient outputs were subsequently spent again.
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 this report.
One of those 5 $BTC payments subsequently 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.
The link to the hack also rests on address attribution, not an identity recorded by Bitcoin. Arkham labels the originating wallets as belonging to the Bitget attacker. The source addresses for these five transactions also appear in the attacker-address API linked from Bitget’s official incident page, corroborating their connection to the exchange’s investigation.
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 and said withdrawals were fully restored on Oct. 2. Fund tracking and recovery remain ongoing, the exchange said.