What happened.

CryptoSlate reports that about 2,746 ZEC, valued at roughly $3.9 million, entered Zcash’s Ironwood shielded pool in three transactions on Wednesday. The report attributes the finding to ZachXBT. Decrypt says the move followed NEAR Intents turning away the Bitget hacker’s swaps.

The transfers matter because funds entering a shielded pool become harder to trace, as CoinDesk’s report describes. The sequence also gives security and compliance watchers a specific development to follow as services handle funds linked to the theft. The supplied record does not establish where the ZEC went after entering the pool.

The wider incident.

SlowMist separately traced malicious activity to an Aug. 31 zero-day exploit involving two security products and a custom withdrawal tool, according to the upstream research summary. That finding places reported attacker activity weeks before the theft, though the supplied record gives no underlying investigation details.

Bitget CEO Gracy Chen says the exchange’s protection fund absorbed a $388 million user loss. A separate Cointelegraph headline puts the fund at $309 million. The supplied record does not explain how those figures relate, so neither figure establishes the fund’s remaining capacity.

What to watch

Watch for documented further inflows into the Ironwood pool and for exchanges’ stated handling of ZEC deposits linked to the theft.

Sources and limits

Upstream references and independent checks

Digest dated 2026-10-01 · upstream model sonnet. Direct links are matched to all 5 upstream source IDs.

  1. 1
    Bitget’s hackers turn to Zcash after $50 million laundering route gets blockedDirect upstream source · 8a93b25fb8ad4da794f5fb54547a81ad5728461d
  2. 2
    Bitget Hacker Turns to Zcash Privacy Pool After Near Rejects $50M in SwapsDirect upstream source · f4a46265450e68c3fc0457107a27504336ed1e96
  3. 3
    Bitget hackers move $4 million into Zcash’s private pool, making funds harder to traceDirect upstream source · 7e7234fe76910a363fb2d4ee80ab1cd658653a03
  4. 4
    SlowMist traces Bitget hack activity to Aug. 31 zero-day exploitDirect upstream source · 9d2c64be7b3f9e3a86876168fd25af9b6ad122f1
  5. 5
    Bitget ‘gradually back to usual’ as protection fund reaches $309MDirect upstream source · c5a51f072a622d03bea05e641d9fe63c14ec9d0b
Continue reading
  1. 1
  2. 2
  3. 3

This Research brief was generated by GPT-6 Sol from a dated upstream research digest. It has not received the source-by-source human review required for Reviewed analysis. Material limit: The supplied record provides reporting summaries and source metadata, but no transaction identifiers or primary investigation documents with which to independently verify the transfers or their subsequent path.