TL;DR
Get hardware and tech essentials delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
Wallets linked to the September 24 Bitget breach moved 2,746 ZEC, worth about $3.9 million, into Zcash’s Ironwood shielded pool on Wednesday. The pool hides transaction details internally, though investigators may compare public deposits and withdrawals using timing, amounts and other metadata.
Wallets linked to the September 24 Bitget breach moved about $3.9 million in Zcash (ZEC) into Zcash’s Ironwood shielded pool on Wednesday, according to CoinDesk’s review of transaction records. The three transfers make the funds harder to follow within the pool while Bitget seeks to recover assets from a breach valued at $387.5 million.
The transfers sent 2,746 ZEC into Ironwood between 08:15 and 08:46 UTC, CoinDesk reported. The deposits represent about 15% of the ZEC stolen in the breach. The transactions were visible as funds entered the pool, but their subsequent movement inside it is not publicly laid out as a traceable transaction trail.
Pseudonymous blockchain investigator ZachXBT flagged the movements earlier Wednesday. He said the funds came through two intermediary addresses funded by a wallet Bitget identified as belonging to the attacker. That wallet received nearly 18,917 ZEC during the September 24 breach, according to the report.
Zcash supports both public and shielded payments. Public records show the amount crossing into Ironwood, while transfers inside the pool conceal the sender, recipient and transfer amount. The report does not establish who controls the intermediary addresses or whether the funds have moved again since the deposits.
How Shielding Changes Fund Tracking
The deposits change what investigators can directly observe on the blockchain. Before funds enter Ironwood, public records can show the transfer amount and the address sending it. Inside the shielded pool, those details are concealed, leaving investigators without a public transaction trail that directly connects one shielded transfer to another.
That makes tracing more difficult, but the movement does not erase the public record of the deposits. If funds later leave the pool for a public address, the withdrawal amount will be visible. Investigators may compare that amount and its timing with the earlier deposits, alongside other metadata, to assess whether the transactions could be related. Such comparisons can help track funds, but the report does not say they would by themselves establish a definitive link.
The amounts matter to the broader recovery effort because the three deposits account for about 15% of the stolen ZEC, not 15% of the full $387.5 million breach. The report describes other proceeds moving across blockchains through swap services. Those routes can leave a different kind of public record: CoinDesk previously traced about $6.3 million in ether-to-bitcoin swaps through THORChain from an attacker-linked wallet.
Top picks for "bitget hacker move"
As an affiliate, we earn on qualifying purchases.
From Breach to Shielded Deposits
Bitget’s reported breach took place on September 24 and was valued at $387.5 million. The attacker-linked wallet identified in the report received nearly 18,917 ZEC during that incident. The later Ironwood deposits were made six days afterward, according to the dates in the source material.
The reported route to Ironwood involved two intermediary addresses funded by the wallet Bitget identified as belonging to the attacker. CoinDesk’s review located three deposits on Wednesday morning. ZachXBT had also flagged the movements, though the source does not provide a direct quotation from him or further details of his investigation.
The Ironwood pool is Zcash’s newest shielded pool, according to the report. Its privacy function means public observers can see funds enter or exit but cannot inspect a public sequence of transfers while funds remain inside. By comparison, the previously reported THORChain swaps left visible records of incoming ether and outgoing bitcoin.
What the Public Record Cannot Show
The public data described in the report does not show who controls the funds now, whether they have moved inside Ironwood, or whether any have left the pool since the three deposits. It also does not establish that the funds can be recovered or identify the people behind the attacker-linked wallets.
If funds return to public addresses, investigators can compare visible amounts and timing with the earlier deposits, as well as other metadata. However, Zcash does not expose a transaction trail linking an exit to a specific entry. The source does not describe any successful match between the Ironwood deposits and a later withdrawal.
The reported dollar value is an estimate tied to the amount of ZEC transferred. The source does not specify the valuation timestamp or provide a price baseline. The size of the wider breach is reported as $387.5 million, but the supplied material does not detail Bitget’s recovery progress, the amount recovered, or the status of any law enforcement investigation.
Possible Clues at Pool Exit
A later withdrawal from Ironwood to a public address could create a new visible point for investigators to examine. They may compare the withdrawal amount and timing with the three deposits and other available metadata. That approach could narrow possibilities, but the available account does not say when any funds might leave the pool or whether an exit would make them identifiable.
Further updates may clarify whether the attacker-linked funds move again, whether investigators identify additional transfers, and what recovery steps Bitget takes. For now, the reported development is limited to the three deposits totaling 2,746 ZEC; the funds’ movements within Ironwood and any subsequent recovery remain unknown.
Key Questions
How much did the wallets move into Ironwood?
CoinDesk’s review found 2,746 ZEC deposited in three transfers, worth about $3.9 million in the report.
Why are the funds harder to trace inside the pool?
Zcash’s shielded pool conceals the sender, recipient and transfer amount for transactions inside it. Public observers can see funds enter the pool, but the pool does not expose a public trail connecting one internal transfer to another.
Can investigators still follow the funds?
If funds later leave for public addresses, the withdrawal amount becomes visible. Investigators may compare timing, amounts and other metadata with the deposits, although Zcash does not itself link a specific exit to a specific entry.
What share of the stolen funds entered Ironwood?
The three deposits represent about 15% of the ZEC stolen in the September 24 breach. That percentage refers to the stolen ZEC, not to the full reported $387.5 million value of the breach.
Source: rss
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
