Hackers behind the Bitget exchange breach have reportedly moved stolen Zcash (ZEC) into Zcash's shielded pool, a privacy feature designed to make transactions harder to trace. According to reporting by CryptoSlate, the switch to Zcash came after a previously used laundering route was blocked.

What Was Reportedly Moved and Where It Went

Per CryptoSlate's report, the individuals behind the Bitget hack turned to Zcash after an earlier attempt to move the funds was shut down, with the stolen ZEC then directed into Zcash's shielded pool following that disruption.

The Bitget incident has already involved significant sums. The exchange restored BTC, ETH, and USDT withdrawals after a reported $387 million hack, and later restored Bitcoin withdrawals following a September 24 security incident. The alleged movement of ZEC into the shielded pool marks what is reported to be a new phase of that activity.

Important caveats apply: wallet attribution and the precise origin of the funds have not been independently confirmed at the time of publication. The claim rests on a single report and has not been verified by publicly released on-chain forensics.

Why the Shielded Pool Draws Attention

Zcash supports two types transactions: transparent and shielded. Transparent transactions resemble Bitcoin's model, in which the sender, receiver, and amount are visible on the public blockchain. Shielded transactions, by contrast, use cryptographic technology to hide those details from public view, as explained in Zcash's own documentation. The protocol also provides viewing keys, which let users selectively disclose transaction details to third parties such as auditors or compliance teams.

Moving funds into the shielded pool does not make them permanently untraceable or guarantee the sender's anonymity. Blockchain analysis firms have developed tools to identify patterns around shielded pool activity, and law enforcement has successfully tracked shielded funds in past investigations. A transfer into a privacy feature does not, by itself, prove criminal intent or confirm the identity of a specific actor.

The shielded pool does, however, raise the difficulty of following funds relative to a standard on-chain transfer. That difference matters operationally: on transparent chains, exchanges and services can flag addresses linked to an attack and freeze incoming deposits, while shielded activity limits those standard interdiction options. That is why investigators and exchanges pay particular attention when stolen cryptocurrency reportedly enters privacy-focused transaction layers.

What Remains Unconfirmed

Several critical details are still unverified. The specific wallet addresses involved, the total amount of ZEC moved, and the exact timeline of the transfer have not been confirmed by independent blockchain analysis or by official statements from Bitget or law enforcement.

Developments worth watching include any official response from Bitget, published findings from blockchain analysis firms, law enforcement action tied to the broader hack investigation, or subsequent movement of the funds out of the shielded pool. Until one of those occurs, the reported transfer should be treated as an unconfirmed claim from a single source.

For anyone holding ZEC or following the broader Bitget situation, the key takeaway is straightforward: a credible outlet has reported that stolen funds may have entered a privacy layer, which complicates recovery efforts, but no confirmed evidence has been published to fully establish the claim.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.