Humanity Protocol: ZachXBT Doesn't Buy the Story. $32 Million Is Gone Either Way.

H token hit $0.85 on June 2. Seven days later 17 wallets were drained, 100 million tokens minted from nothing, and $32 million converted to ETH. ZachXBT called it possibly staged. The team blamed one compromised laptop. Neither story is complete.

Humanity Protocol's H token hit an all-time high of $0.85 on June 2, 2026. Seven days later $32 million was gone and ZachXBT publicly called the 'hack' possibly staged - a market maker exit disguised as a private key compromise

On June 2, 2026, the H token hit $0.85. That was the top. The token had run 875% from its January lows, fuelled by Mastercard and Fireblocks partnership announcements and the AI-adjacent narrative around biometric identity. Humanity Protocol lets users verify their humanity through biometric scans, then issues credentials on a blockchain. Think of it as the decentralised alternative to Sam Altman's Worldcoin. In 2026, that was a narrative investors were willing to pay for.

Seven days later, $32 million was gone.

Specter, the on-chain analyst, was first to flag it on June 9. More than 17 wallets linked to Humanity Protocol were being systematically drained. Initial losses looked like $5 million. Within hours the number was $32 million.

On Ethereum, attackers upgraded the project's bridge contract to a malicious implementation. They gained control over outgoing transactions and drained 141 million H tokens, converting them to ETH. Simultaneously, the attack extended to BNB Chain. The attackers seized ProxyAdmin control of the H token contract there. With ProxyAdmin access they could do anything. They minted 100 million H tokens from the null address. From nothing. Then sold those too.

By the end, the attacker had converted everything into 18,510 ETH worth $30.83 million and 1,548 BNB worth $924,000. Another 111 million H tokens worth roughly $14 million at pre-crash prices sat in attacker-controlled addresses. On-chain liquidity had been nearly exhausted. That remaining 111 million was essentially unsellable.

H crashed from $0.85 to $0.05 - a 94% collapse in a single session. Daily volume exceeded $600 million as holders scrambled to exit. The project paused operations and warned users to avoid its bridges and liquidity pools.

The team's explanation: a private key belonging to a core team member had been compromised. One laptop. Everything followed from that one breach. They launched a $1 million USDT bounty for information and began compiling a compromised-address tracker.

ZachXBT did not accept the explanation.

He posted: "The incident seems possibly staged. I am not buying the team's story it's a convenient way for the active MM to have exited."

He followed with: "You choose to crime pump your token for weeks with zero fundamentals and think CT will blindly trust your story? Disclose your active MM agreements with the HK entity first."

Independent analyst Elton found details that supported the read. The attacker's wallets had been pre-funded weeks before the incident, with capital from an exchange and a mixer arriving in late April and May - well before the attack. The minting authority on the BNB Chain contract had been tested and warmed up days before the exploit executed. The coordinated timing across Ethereum and BNB Chain simultaneously indicated advance planning, not an opportunist who had just obtained a stolen key.

Then ZachXBT walked some of it back. After further analysis, he said the private key compromise and the separate market-making irregularities appeared to be unrelated events that coincided. The picture was more complicated than his initial read.

Two things are true simultaneously. The private key compromise is confirmed. The market-making irregularities ZachXBT identified are also confirmed. Whether those two things are connected or coincidental is the question nobody has answered.

One more detail. H had a token unlock scheduled for June 25. Another 105 million tokens were set to enter circulation. Whether the timing of the hack relative to that date was designed or coincidental, it did not help anyone already holding.

As of June 14, 2026, no funds have been recovered. No attacker has been identified. The $1 million bounty has produced no public leads. H trades at a fraction of its all-time high. The investigation is ongoing.

Humanity Protocol is still alive. The token is not.