Crypto Scam: On-Chain Data Tracks More Stolen Funds Moving Into Zcash
Published Updated 3 new reports since it was first published
On-chain tracing again showed stolen funds moving into Zcash shielded pools, with one report tying transfers to losses from Ledger and Bitget. Separate coverage also said investigators had previously traced about 2,746 ZEC to the Bitget breach, and that SlowMist and Mandiant confirmed Bitget losses of $387.5 million across 11 blockchains.
What this rests on
What it means
Zcash has offered optional shielded transactions since 2016, a feature that routes funds through zk-SNARK pools so that sender, receiver and amount are hidden from the public ledger, unlike Bitcoin's fully transparent chain. That design has made it a recurring reference point alongside Monero whenever stolen funds go dark, and the Bitget breach gives the comparison fresh weight: SlowMist and Mandiant have confirmed losses of $387.5 million spread across eleven blockchains, a scale that puts pressure on any destination chain tied to the laundering trail.
Exchanges and compliance teams now face a narrower set of options once funds enter a shielded pool: tracing stops at the point of entry, so any exchange that still lists ZEC withdrawals or deposits has to decide whether to flag, delay or freeze transactions tied to known hacker addresses before they shield, since nothing can be done after. Bitget's own response, closing some customer accounts following the breach, shows the kind of blunt action platforms take when they cannot follow funds further; investigators are left working the Ledger and Bitget cases backward from known entry points rather than forward through the chain. Holders of ZEC who have nothing to do with either breach now carry the reputational weight of being associated with a laundering route, a cost privacy-coin users have faced before with Monero delistings.
Shielded transactions are not evidence that Zcash itself was compromised, and conflating a privacy feature with a security failure misreads what happened: the network functioned exactly as designed, and privacy remains a legitimate, even necessary, property of a monetary system rather than a loophole to be closed. The harder question is whether a chain that offers strong on-chain privacy can keep serving legitimate users once exchanges and regulators treat every shielded deposit as a laundering signal, the same bind that has already narrowed Monero's exchange listings in multiple jurisdictions. Tracing firms can watch the pool's edges but not its interior, which means the burden of proof keeps shifting onto the coin's ordinary holders rather than onto the thieves.
Market reaction
The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.
How the story was built
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| today | Slice incident | $41k |
| 3 days ago | AlpsCon AI Trade Hub · Incorrect Share Accounting incident | $152.8k |
| 3 days ago | Argent-style Smart Wallet System incident | $59.8k |
| 4 days ago | Coffer · Rounding Error incident | $1 |
| 4 days ago | AlpsCon (~152.8K USDC) incident | no figure in dollars |
4215 incidents stored