{"id":24124,"date":"2026-06-10T05:32:13","date_gmt":"2026-06-10T05:32:13","guid":{"rendered":"https:\/\/nft.runfyers.com\/index.php\/2026\/06\/10\/humanity-protocols-h-token-crashes-over-80-after-36m-private-key-breach\/"},"modified":"2026-06-10T05:32:13","modified_gmt":"2026-06-10T05:32:13","slug":"humanity-protocols-h-token-crashes-over-80-after-36m-private-key-breach","status":"publish","type":"post","link":"https:\/\/nft.runfyers.com\/index.php\/2026\/06\/10\/humanity-protocols-h-token-crashes-over-80-after-36m-private-key-breach\/","title":{"rendered":"Humanity Protocol\u2019s H Token Crashes Over 80% After $36M Private-Key Breach"},"content":{"rendered":"

<\/p>\n

\n

Humanity Protocol\u2019s H token<\/b> plummeted by over 80% on June 9 after the project confirmed an exploit involving compromised private keys, resulting in the theft of over $36 million in tokens and their dumping onto the market.<\/span><\/p>\n

In a post-mortem published on the evening of June 9, Humanity stated that the incident occurred between June 8 and June 9 via <\/span>three attack vectors<\/b> across Ethereum and BNB Smart Chain. These included direct theft from an admin hot wallet, a bridge drain on Ethereum, and the unauthorized minting of 300 million H tokens on BSC. The project noted that the root cause was malware on an internal machine that had mistakenly stored multiple production keys, turning a breach on a personal device into a crisis at the bridge admin and token supply level.<\/span><\/p>\n

How the Exploit Happened<\/b><\/h3>\n

Humanity initially stated that the incident stemmed from a laptop breach by an internal staff member. The <\/span>post-mortem<\/span><\/a> later clarified a more severe detail: a device had been compromised with root access via malware, while multiple production keys had been mistakenly backed up to it during the mainnet launch phase around June 2025.<\/span><\/p>\n

\n

INCIDENT UPDATE:<\/p>\n

Last night, June 8, the H token was hit by a coordinated attack across Ethereum and BSC. While we\u2019re still investigating this incident, we want to be transparent with our community about what happened.<\/p>\n

As of right now, ~$36M+ has been stolen across both chains\u2026<\/p>\n

\u2014 Humanity (@Humanityprot) June 9, 2026<\/a><\/p>\n<\/blockquote>\n

From this compromise point, the attacker obtained enough keys to operate on both Ethereum and BNB Smart Chain. On Ethereum, the attacker seized control of the <\/span>Bridge ProxyAdmin<\/b>, upgraded the bridge to a malicious version, and withdrew approximately 141.18 million H tokens in a single transaction. An admin hot wallet was also drained of an additional 6.05 million H tokens.<\/span><\/p>\n

On BNB Smart Chain, the incident went further than a bridge drain. The attacker compromised the ProxyAdmin of the BSC H token and minted 300 million H tokens across three iterations on June 9. The supply of H on BSC surged from around 141.12 million H to 441.12 million H, expanding the supply on this chain to over three times its pre-attack level.<\/span><\/p>\n

According to Humanity, this was not a smart contract flaw in the traditional sense. The attacker signed transactions using valid private keys after internal key storage was compromised, turning an operational failure into control over the bridge and token admin across multiple chains.<\/span><\/p>\n

H Token Erases Early-June Rally<\/b><\/h3>\n

H had rallied strongly prior to the incident, climbing from the $0.20 region in late May to a short-term peak near $0.855 in early June. Following the exploit, the token dropped below $0.10 across several venues, with charts recording a low of around $0.074 before recovering to the $0.16-$0.22 zone.<\/span><\/p>\n