Bitget hackers move $4 million into Zcash’s private pool, making funds harder to trace
Wallets tied to the September 24 Bitget breach moved roughly 2,746 ZEC — about $3.9 million — into Zcash’s Ironwood shielded pool in three transfers on Wednesday, obscuring sender, recipient and amount details inside the private pool. The deposits account for about 15% of the ZEC taken in the $387.5 million hack, according to transaction records and blockchain investigator reports.

Why It Matters
Putting stolen funds into Zcash’s shielded pool makes on-chain tracing far more difficult for investigators and for the exchange seeking recovery, because Ironwood conceals inside-pool transaction details even though entry and exit amounts remain visible. That mixing of stolen proceeds with privacy-preserving infrastructure complicates asset recovery and forensics for a high-profile exchange heist.
Key Facts
- Date of Bitget breach: Sept. 24, 2026
- Total value of Bitget hack: $387.5 million
- ZEC moved into Ironwood: 2,746 ZEC
- USD value of ZEC moved: About $3.9 million
- Number of transfers into Ironwood: Three transfers between 08:15 and 08:46 UTC on Sept. 30, 2026 (reported)
Wallets linked to the Sept. 24 Bitget security breach directed about 2,746 zcash (ZEC) into Zcash’s Ironwood shielded pool on Wednesday, a move that hides transaction details from public view. Chain records reviewed by reporters show the funds arrived in three separate deposits between 08:15 and 08:46 UTC, totaling roughly $3.9 million and representing about 15% of the ZEC stolen in the hack. The deposits were routed through two intermediary addresses that were funded by a wallet Bitget identified as controlled by the attacker. Pseudonymous investigator ZachXBT flagged the movements and traced their origin to the attacker-linked wallet, which received nearly 18,917 ZEC during the initial breach. Zcash supports both transparent and shielded transactions. Transfers into Ironwood are visible as entries on-chain, but once inside the shielded pool the sender, recipient and individual transfer amounts are concealed. That means while investigators can observe the amounts that went into Ironwood and any amounts that later exit to public addresses, the protocol does not provide a direct transaction trail linking the two. Some other proceeds from the Bitget incident have been moved across blockchains through swap services. CoinDesk previously traced about $6.3 million in ether-to-bitcoin swaps via THORChain from one attacker-associated wallet, actions that left public records of the incoming ether and outgoing bitcoin. The Ironwood deposits, by contrast, increase complexity for tracing efforts and for Bitget’s ongoing recovery attempts.
Keep Reading

The SEC Is finally modernizing transfer-agent rules. Wall Street must not repeat the ‘paperwork crisis’

Clock's ticking: UK's crypto regulatory application window opens with February deadline

Crypto Long & Short: What will the AI agents run on?
