|

Failed Ethereum ICO from 2016 just unlocked 1,003 ETH by exploiting itself

Someone just drained long-forgotten dormant Ethereum wallets, and the cause may trace back years

A white-hat researcher’s restoration of 1,003.62 ETH from a failed 2016 Ethereum ICO has turned an previous sensible contract flaw right into a reminder that Ethereum’s earliest technical choices can stay stay for practically a decade.

The researcher, often known as 0xFlorent, stated he unlocked the ETH from the HongCoin contract after the funds had been trapped for 9 years. Using a June 1 Ethereum value of roughly $1,983, the recovered quantity was value about $1.99 million.

The restoration trusted the unique HongCoin multisig. The HongCoin contract nonetheless required motion from that administration path for the related admin calls.

That made the episode nearer to contract archaeology than to a traditional exploit: the identical immutable code that preserved the refund failure additionally preserved a forgotten route round it.

Someone just drained long-forgotten dormant Ethereum wallets, and the cause may trace back years
Related Reading

Someone just drained long-forgotten dormant Ethereum wallets, and the cause may trace back years

Hundreds of long-inactive Ethereum wallets were swept into a tagged address while researchers and users still debate whether old keys, weak wallet tooling, or another exposure opened the door.
May 1, 2026
·
Liam ‘Akiba’ Wright

HongCoin’s distinction is stark. Ethereum’s base layer stayed nonetheless. A still-valid permission path and coordinated signing from the unique multisig made 48 unique buyers eligible to say funds via a refund mechanism that had been damaged for years.

How the refund path broke

HongCoin was a 2016 Ethereum venture whose public repository described it as a decentralized venture fund. The token sale failed to succeed in its funding aim, and contributors had been supposed to have the ability to reclaim their ETH via the contract’s refund perform.

The downside sat contained in the contract’s accounting. In the HongCoin source code, the refundMyIcoInvestment() perform checks whether or not the caller’s token stability is larger than tokensCreated. If that situation is true, the refund name fails.

If it passes, the perform zeroes the caller’s token stability, clears associated accounting, reduces tokensCreated by that token stability, after which sends the refund.

Over time, earlier refunds decreased the worldwide tokensCreated counter. That left bigger holders in an odd place: they nonetheless had balances tied to their unique claims, however these balances could possibly be too massive for the contract’s remaining counter.

The refund perform then handled them as invalid, blocking the very customers it was purported to repay.

The escape path was one other previous piece of code. The multisig-restricted mgmtIssueBountyToken() admin perform might add a provided quantity to a recipient’s stability and to bountyTokensCreated.

That path belonged to the administration aspect of the contract, which is why the unique multisig needed to take part. Modern Solidity arithmetic reverts by default on overflow.

Before Solidity 0.8.0, arithmetic wrapped on overflow until builders added their very own checks. The older habits formed the escape route.

0xFlorent recognized a manner to make use of the admin perform’s arithmetic habits to reset a holder’s stability low sufficient for the refund verify to go. The outcome was paradoxical: one stale bug helped undo the sensible injury prompted by one other stale bug.

Stage Key element
2016 token sale HongCoin collected ETH for a venture-fund-style Ethereum venture that later failed to succeed in its aim.
Refund failure The refund perform rejected bigger holders as soon as the worldwide token counter fell beneath their balances.
Old admin path A multisig-restricted perform nonetheless existed that might change balances utilizing pre-0.8 Solidity arithmetic habits.
Whitehat restoration 0xFlorent coordinated with the unique HongCoin multisig to make blocked holders eligible to say funds.
On-chain proof A May 29 transaction exhibits a profitable refundMyIcoInvestment() name producing an inside 96 ETH switch.

Flow diagram showing how HongCoin's 2016 failed ICO, refund accounting bug, original multisig, and integer-overflow path unlocked 1,003.62 ETH.

The multisig made it a coordinated restoration

The multisig requirement set a boundary for the HongCoin restoration. The delicate path required HongCoin’s unique administration tackle to execute the related calls, so the sensible restoration trusted cooperation between the researcher and the previous management path.

The coordination carried as a lot weight because the code. The restoration concerned 41 signed transactions for blocked holders, whereas one other seven smaller holders might refund immediately with out the workaround.

The ICO started on Aug. 29, 2016, ended on Oct. 28, 2016, and failed to fulfill its funding aim.

The on-chain report already exhibits refund exercise. A May 29 on-chain transaction referred to as refundMyIcoInvestment() and produced an inside switch of 96 ETH from the HongCoin contract to an investor tackle.

The top-level transaction worth was 0 ETH as a result of the precise motion occurred contained in the contract name.

Anyone following the cash ought to separate eligibility from accomplished distribution. The contract state and multisig execution reopened a declare path for funds that had been inaccessible for years.

The seen on-chain examples present refund exercise fairly than a full accounting of each eligible investor’s declare.

The HongCoin case must be learn rigorously earlier than anybody generalizes it to different previous caught funds. The elements had been unusually particular: identifiable contract logic, an admin perform nonetheless usable by the unique management path, a whitehat keen to coordinate, and sufficient remaining on-chain worth to take the time worthwhile.

The sensible element is possession and permission. The previous perform might change balances, however solely the administration path might name it.

That provides the restoration its moral and operational boundary: outdoors analysis discovered the trail, unique signers executed it, and the declare route reopened for buyers.

Aave warns $71M exploit recovery could be seized before victims are repaid
Related Reading

Aave warns $71M exploit recovery could be seized before victims are repaid

The dispute could decide whether DeFi recovery funds go back to users first or become targets for outside creditors.
May 5, 2026
·
Gino Matos

The similar info additionally make the case onerous to generalize. Many dormant contracts lack an energetic management key, a clear claimant set, or a public path that makes accountable restoration believable.

That boundary additionally reduces the temptation to deal with the episode as a broad exploit template. The technical mechanism explains why the refund gate reopened, however the story’s consequence comes from the mixture of previous code, dwelling permissions, and public settlement.

Similar archaeology turns into riskier when a contract lacks a kind of components, as a result of discovery can expose a weak spot earlier than it creates a usable restoration route.

Ethereum retains the error and the treatment

The broader Ethereum historical past makes the HongCoin restoration greater than a curiosity. A 2025 analysis citing Coinbase’s Conor Grogan put completely misplaced ETH at greater than 913,111, framed as a conservative estimate throughout consumer and contract-related errors.

That class contains funds despatched to burn addresses, contract bugs, and main historic incidents.

Some of Ethereum’s most consequential early moments had been additionally restoration debates. In 2016, the DAO hard fork moved roughly 12 million ETH from DAO-related contracts right into a restoration contract after the community’s defining governance disaster.

In 2017, Parity Technologies’ multisig library self-destruct incident blocked 513,774.16 ETH throughout 587 wallets.

Those episodes had been bigger and politically heavier than HongCoin. They nonetheless assist body why this smaller restoration resonates.

Timeline matrix showing Ethereum stuck-fund history, including The DAO, Parity, lost ETH estimates, and the 2026 security endowment plan.

Ethereum’s promise that code and state persist is a safety property and a reminiscence system. It preserves errors, half-forgotten assumptions, previous permissions, and the occasional treatment whose future relevance was invisible at deployment.

TheDAO’s leftover rescue money sat for a decade now it’s becoming Ethereum’s permanent $220M security budget
Related Reading

TheDAO’s leftover rescue money sat for a decade now it’s becoming Ethereum’s permanent $220M security budget

Veterans want to stake 69,420 ETH from leftover 2016 recovery funds, generating millions yearly for smart contract security.
Jan 30, 2026
·
Gino Matos

That lengthy reminiscence now sits beside a maturing safety tradition. In January, Ethereum veterans announced plans to transform roughly 75,000 ETH in leftover TheDAO restoration funds right into a staked endowment for Ethereum safety.

Comic-style image of an Ethereum treasure chest marked HongCoin ICO, showing explorers recovering 1,003.62 ETH.

The HongCoin case works on a a lot smaller scale, however factors to the identical afterlife of early Ethereum choices.

The subsequent check is recoverability: whether or not different previous contracts comprise paths that can be utilized responsibly. A white-hat restoration wants greater than a bug. It wants a rightful management path, public on-chain proof, cautious disclosure, and a technique to keep away from turning contract archaeology right into a playbook for opportunistic assaults.

HongCoin exhibits that some trapped funds can stay suspended inside previous logic, ready for somebody to know each the flaw and the permission construction round it. That is a hopeful outcome for the 48 buyers now eligible to say.

It can be a warning for the remainder of the ecosystem: Ethereum remembers unhealthy code, and generally it remembers the escape hatch too.

The publish Failed Ethereum ICO from 2016 just unlocked 1,003 ETH by exploiting itself appeared first on CryptoSlate.

Similar Posts