Skip to main content
AVOID.NET
← Hemi (Genesis Drop / MerkleBox Exploit)reviewed 2026-10-27 · 9 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Hemi (Genesis Drop / MerkleBox Exploit) 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 3partially supported 1confirmed 50 corrections pending · 0 applied

unverifiable

3 claims

No source the reviewer could reach confirms or contradicts the claim.

  1. #3[unverifiable][awaiting moderator]in section: Genesis Drop MerkleBox Exploit — Technical Details
    “making 63 recursive calls within a single transaction”
    reviewerExploit made 63 recursive callsThe count was not found in the fetched version of the postmortem relay; other cited sources were not checked for it.
  2. #4[unverifiable][awaiting moderator]in section: Fund Exfiltration and Cross-Chain Movement
    “approximately $151,524.70 USDT and $103,422.62 USDC per the official postmortem”
    reviewerPrecise USDT/USDC split per official postmortemInternal inconsistency: 158,200 + 84,900 = ~243,100, versus 151,524.70 + 103,422.62 = ~254,947. The page should reconcile the figures.
  3. #8[unverifiable][awaiting moderator]in section: Protocol Overview
    “Hemi's mainnet launched in March 2025.”
    reviewerHemi mainnet launched in March 2025 (March 12)Not fetched. The cited article title says a March 12 launch was planned, not that it occurred; the timeline states it as fact.

partially supported

1 claim

The cited evidence supports part of the claim but not all of it.

  1. #9[partially supported][awaiting moderator]in section: Scope Limitation and Containment Assessment
    “No user funds held in wallets, liquidity pools, or the core protocol were directly at risk from this exploit.”
    reviewerThe stolen tokens were unclaimed airdrop allocations; no user funds at riskThis is a project self-assessment stated as fact. Unclaimed airdrop recipients lost their allocation, which the page does not state.

confirmed

5 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in the summary
    “draining approximately 124.5 million unclaimed HEMI tokens, which were liquidated for roughly $255,000 in stablecoins”
    reviewerExploit occurred at 03:36:47 UTC on Sept 7, 2026, draining ~124.5M unclaimed HEMI, sold for ~$255,000Amount, date, time and proceeds match the postmortem relay and independent reporting.
  2. #2[confirmed][no action needed]in section: Genesis Drop MerkleBox Exploit — Technical Details
    “A flash loan of 2 million HEMI tokens was borrowed from the HEMI/USDT pool on SushiSwap to satisfy the staking threshold required to register a claim group; the loan was repaid atomically within the same transaction.”
    reviewerFlash loan of 2M HEMI from SushiSwap HEMI/USDT pool repaid atomicallyLoan source and atomic repayment confirmed; the purpose detail was not independently seen.
  3. #5[confirmed][no action needed]in the timeline
    “Upbit cancelled its planned HEMI listing approximately 18 minutes before the scheduled 9:30 p.m. KST opening, citing the exploit and apparent token theft.”
    reviewerUpbit cancelled HEMI listing ~18 minutes before 9:30 pm KST on Sept 8Confirmed.
  4. #6[confirmed][no action needed]in the timeline
    “Bithumb designated HEMI as a trading warning asset and suspended HEMI deposits at 11:50 KST, citing the smart contract vulnerability, abnormal token outflow, and inadequate timely disclosure.”
    reviewerBithumb warning designation and deposit suspension at 11:50 KST citing vulnerability, outflow and late disclosureMatches the source.
  5. #7[confirmed][no action needed]in the timeline
    “05:42 UTC — Hypernative security monitoring platform alerted the Hemi team to the exploit.”
    reviewerHemi alerted by Hypernative at 05:42 UTCConfirmed via the postmortem relay; the cited KuCoin page was not fetched.
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.