Ten years after The DAO, reentrancy is still draining contracts. Hemi Network, the Bitcoin-Ethereum layer-2 project, has published a post-mortem confirming that its Genesis Drop token distribution was exploited through exactly this flaw on September 7, at 03:36:47 UTC — with an attacker draining 124.5 million HEMI tokens from a claim contract for a realized value of roughly $255,000.
The incident's anatomy matters more than its price tag.
What Was Hit — and What Wasn't
The target was a contract known internally as MerkleBox, which held unclaimed Genesis Drop allocations — tokens that had never reached user wallets. The attacker did not touch Hemi's core network, its native HEMI or veHEMI tokens, the Hemi Virtual Machine, or any bridging infrastructure. The blast radius ended at one distribution contract.
That containment is the post-mortem's central mitigating fact, and Hemi leaned on it in its public statements. But the structural lesson cuts the other way: the claim contract was immutable once deployed, so the flaw could not be patched — only worked around after the fact.
How the Drain Worked
Per the post-mortem and subsequent analyses, the attacker used a flash loan to fund a recursive call loop — reported at 63 recursive calls — repeatedly re-entering the claim function before the contract's accounting updated the claimed balance. It is the same check-interactions-effects failure that emptied The DAO in 2016 and defined an era of Ethereum security engineering.
By the numbers, the exchange rate is stark: 124.5 million tokens moved for about $255,000, because the stolen HEMI had shallow liquidity to exit through. The attacker liquidated and bridged the tokens across multiple chains within roughly a day. No recovery has been reported.
The Consequences Beyond the Loss
The market damage exceeded the theft. Upbit, South Korea's largest exchange, withdrew its planned HEMI listing days before it was to go live — a decision that removes the liquidity event a Genesis Drop exists to precede. For token-launch infrastructure, the incident is a case study in how a low-dollar exploit can still be existential: the bug class is old, the contract was unpatchable, and the listing partner walked.
Reentrancy's rarity makes the miss harder to excuse, not easier. Sector analyses of aggregated audit-firm data place reentrancy at roughly 6-8% of high-severity findings in 2026, down from being the single most common finding class between 2018 and 2020. The pattern is well documented, the detection tooling is mature, and the failure mode appears in every audit firm's checklist. A distribution contract shipping with the flaw suggests the claim path was never in a reviewed scope at all — or that no human review covered it.
The distribution-contract blind spot is the takeaway for every project with a token launch ahead of it: airdrop and claim contracts handle the exact operation — external calls interleaved with balance accounting — that reentrancy preys on, and they are frequently deployed on separate timelines from core protocol code.
TrustGrade covers the security and trust ecosystem around digital assets. For verified trust data on the platforms and firms shaping it, see trustgrade.ai.