← Humanity Protocol June 2026 Hackreviewed 2026-11-01 · 11 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Humanity Protocol June 2026 Hack against the sources the page cites. Only the most recent review is shown.
Read this first
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
unverifiable
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #3[unverifiable][awaiting moderator]in section: DPRK Attribution
“On June 12, 2026, Quantstamp published an investigation report concluding that the attack bore”
reviewerQuantstamp report published June 12, 2026Coverage appeared June 13-14. No fetched source states a June 12 publication date. Possible but unsupported. - #4[unverifiable][awaiting moderator]in the timeline
“2026-06-12”
reviewerTimeline entry dates Quantstamp report 2026-06-12 and cites Crypto Briefing, which was published June 14 and does not give the dateSame issue as the section claim. The cited source does not support the stated date. - #8[unverifiable][awaiting moderator]in section: Inside Job Allegations and ZachXBT Investigation
“However, ZachXBT subsequently revised his assessment after further on-chain analysis of fund movements.”
reviewerZachXBT called the incident possibly staged, then revised to a private key compromiseNot fetched, so no verdict is given. The headline in sources_used is consistent with the claim. - #11[unverifiable][awaiting moderator]in the timeline
“Humanity Protocol raises $30 million in funding led by Kingsway Capital at a $1 billion valuation.”
reviewerPantera/Jump $20M round in January 2025 at $1.1B FDV; Kingsway $30M in May 2024Not fetched. The cited Coinspeaker URL covers the $20M round, not the 2024 $30M round, so the source may not match this entry.
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #5[partially supported][awaiting moderator]in section: DPRK Attribution
“The report cited specific malware infrastructure details, a South Korean Hancom certificate-signing behavior, and overall operational tactics frequently observed in attacks attributed to the Lazarus Group and affiliated North Korean cyber units.”
reviewerQuantstamp cited a Hancom certificate-signing pattern and Lazarus Group tacticsHancom is supported by The Defiant, but not by the two sources cited in this section. Quantstamp naming Lazarus specifically is not supported; the sources use only 'DPRK-affiliated' or 'consistent with'. - #7[partially supported][awaiting moderator]in section: Attack Vector and Technical Mechanics
“On June 5, 2026 — three days before the on-chain exploit — a spear-phishing email impersonating South Korean cryptocurrency exchange Bithumb was sent to a Humanity Protocol director with whom Bithumb maintained active communications.”
reviewerSpear-phishing email impersonating Bithumb was sent June 5June 5 start is supported. The Bithumb impersonation was not confirmed because the CryptoTimes source was not fetched.
confirmed
5 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Incident Overview
“The attacker drained approximately 141.18 million H tokens from 17 project wallets on Ethereum and minted an additional approximately 200 million H tokens on BNB Chain using an unauthorized mint function.”
reviewerAttacker drained ~141.18M H on Ethereum and minted ~200M H on BNB Chain; losses ~$36MCore figures match CoinDesk. The '17 project wallets' detail was not verified. - #2[confirmed][no action needed]in section: Attack Vector and Technical Mechanics
“The root cause of the exploit was an operational security failure rather than a smart-contract vulnerability.”
reviewerMultisig keys (3-of-6 Ethereum, 3-of-5 BNB) were stored on one compromised employee laptopConfiguration and cause match CoinDesk. - #6[confirmed][no action needed]in section: DPRK Attribution
“Quantstamp's public report stopped short of definitive attribution and did not disclose specific attacker wallet addresses in its public release.”
reviewerQuantstamp stopped short of definitive attribution and did not release wallet addressesMatches the sources. - #9[confirmed][no action needed]in section: Recovery and Response
“Eligible holders would receive new H tokens on a 1:1 basis based on balances captured at pre-exploit snapshot blocks: Ethereum block 25,274,179, BNB Chain block 103,071,069, and Humanity Mainnet block 24,247,803.”
reviewerRecovery plan with new ERC-20 H token, 1:1 snapshot airdrop, snapshot blocks, compensation fund, mainnet relaunch 'in the coming weeks'Corroborated by search results for The Defiant and others. Not read in full. - #10[confirmed][no action needed]in section: Incident Overview
“The H token price fell from approximately $0.67–$0.72 to an intraday low near $0.05, a decline exceeding 90%, before settling around $0.13–$0.20 by end of day.”
reviewerToken fell from ~$0.67-0.72 to ~$0.05 low and ~$0.20 recoveryConsistent with CoinDesk.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.