Humanity Protocol Drained After Multisig Keys Shared One Laptop

Humanity Protocol was drained on June 9 after an attacker obtained the private keys controlling the project's multisignature wallets, the arrangement in which a set number of separate keyholders must sign before funds can move. CoinDesk reported the loss at $36 million; the blockchain security firm PeckShield logged it at $31 million. The two figures differ, and neither has been reconciled against the other. Founder Terence Kwok said keys intended for four separate people had been "accidentally backed up to a compromised device during setup." The project's H token fell from about $0.67 to as low as $0.05 before recovering to roughly $0.20.

The Mechanics: Two Chains, Two Sets of Keys

The attacker did not break the wallets so much as operate them. On Ethereum, three of six keys were used to drain about 141 million H. On BNB Chain, three of five were used to mint about 200 million new tokens, creating supply rather than merely moving it. Every one of those transactions was valid on its face: the required number of signatures was present, and the contracts executed exactly as written. The two legs of the attack, and the disputed loss figure, stand as follows:

• Ethereum: three of six keys, roughly 141 million H drained.
• BNB Chain: three of five keys, roughly 200 million H minted.
• Total loss: $36 million according to CoinDesk, $31 million according to PeckShield.

Why the Threshold Held Nothing: Independence, Not Arithmetic

A signing threshold is a claim about people, not about cryptography. Requiring three signatures out of six is meant to guarantee that no single person, and no single machine, can move funds alone, and that guarantee rests entirely on the keys living apart from one another: different holders, different devices, different failure modes. Once keys meant for four people were copied onto one laptop, the threshold reduced to whatever protected that laptop. An attacker reaching the device did not have to defeat three independent custody setups. One was sufficient, and it cleared the threshold on both chains at once. The wallet's configuration never changed, which is the hard part of the problem: on-chain, a 3-of-6 wallet whose keys sit in one folder is indistinguishable from one whose keys sit in six safes on three continents.

The Token: A $1.1 Billion Valuation Meets a Five-Cent Print

H's fall from about $0.67 to as low as $0.05 erased the large majority of the token's value before buyers took it back to roughly $0.20, still well below where it traded before the exploit. Humanity Protocol raised $20 million from Pantera and Jump Crypto at a $1.1 billion valuation in 2025, and that backing did nothing to prevent an error in how keys were stored. The roughly 200 million tokens minted on BNB Chain also sit on the price as unbacked supply, a problem distinct from the funds taken on Ethereum and one that recovering the stolen assets would not by itself resolve.

Setup as the Unaudited Step: What the Case Leaves Open

Smart contract code is audited, often repeatedly. The ceremony in which keys are generated, distributed and backed up usually is not. It happens once, early, frequently under launch pressure, and it leaves no record on-chain, which means no user, exchange or auditor can verify from the chain that a published threshold corresponds to genuinely separated custody. That gap is what this incident exposes, and raising the threshold does not close it: a 5-of-9 wallet on one laptop is no safer than a 3-of-6. PeckShield counted $75.87 million stolen across 40 incidents in June, down 7.13% from $81.7 million in May, with this single failure accounting for roughly two-fifths of the month's total on the firm's own figure. Whether teams begin publishing verifiable attestations of where keys are held, rather than only how many are required, is the practical test of whether the lesson lands.