News

Public · Published

Bitget's hackers turn to Zcash after $50 million laundering route gets blocked

Hackers behind the Bitget breach moved about 2,746 ZEC into Zcash's Ironwood shielded pool through three transactions on Wednesday, according to on-chain activity flagged by blockchain investigator ZachXBT.

Published:

Updated:

What happened

Hackers behind the Bitget breach moved about 2,746 ZEC into Zcash's Ironwood shielded pool through three transactions on Wednesday, according to on-chain activity flagged by blockchain investigator ZachXBT.

Confirmed

Global impact / market context

If stolen funds can hide in Zcash's shielded pool, which means a private transaction feature, tracing and recovery become harder. Blocked escape routes may push hackers toward privacy coins, possibly increasing regulatory scrutiny on Zcash.

Analyst inference

The Bitget breach was large, and crypto firms are increasingly blocking other escape routes. That pressure may push demand toward privacy tools like Zcash, though this single transfer is small relative to the total stolen.

Analyst inference

What to watch

  1. ZachXBT flagged three Wednesday transactions moving about 2,746 ZEC into Zcash's Ironwood shielded pool, so follow whether more stolen Bitget funds enter Zcash. Confirmed
  2. If exchanges tighten rules on privacy coins, Zcash's trading access and its ZEC price could face pressure, while other privacy-focused assets might see similar regulatory attention and investor caution. Analyst inference
  3. Investors should track whether regulators propose new restrictions on shielded pools or privacy coins, because such rules could change how Zcash is traded, held, or delisted by major platforms. Proposed

Affected assets

  • ZEC — Zcash
  • RUNE — THORChain

Evidence