Harmony's $ONE Plunges 40% After Attacker Mints Four Billion Tokens Equal to a Quarter of Supply

What Happened

On August 11, 2026, an attacker exploited the Harmony blockchain to mint four billion $ONE tokens without authorisation — an amount roughly equal to one quarter of the network's entire circulating supply at the time. The sudden expansion of the token supply caused the price of $ONE to fall approximately 40% within hours, as markets absorbed the scale of the dilution and uncertainty about the team's response spread across trading platforms. The attacker moved quickly: on-chain forensics conducted by Harmony and independent analysts traced 10,288 individual transfers across 409 wallets, with approximately 2.8 billion of the minted tokens routed toward centralised exchanges in an attempt to off-ramp the proceeds before the network could respond.

Harmony responded by pausing its token bridge, cutting off the primary mechanism through which newly created $ONE could be converted into wrapped representations on other networks — Ethereum, Binance Smart Chain, and others — where sufficient liquidity exists to dispose of large token quantities with less scrutiny. The team also made an emergency request to major centralised exchanges to freeze assets originating from four wallet address clusters linked to the attacker. Whether individual exchanges complied — and how quickly — varied, creating an uneven perimeter during a critical window when the attacker's ability to convert tokens to other assets determined the ultimate real-world loss.

Harmony subsequently published a rollback plan specifying restoration block heights — a set of coordinates that would allow the network's validators to agree on reverting chain state to the point immediately before the exploit. Rollbacks are among the most controversial responses available to a public blockchain project. They directly contradict the promise of immutability that gives decentralised networks much of their value, and they become progressively less effective the longer an attacker has had to move assets off-chain. Any $ONE already converted to other tokens on centralised platforms would not be recoverable through a chain revert.

This incident is the third significant security event in Harmony's history in under three years. In June 2022, attackers later confirmed by the United States Federal Bureau of Investigation to be the North Korean Lazarus Group (APT38) stole approximately $100 million from the Horizon Bridge by compromising private keys held by the bridge's multisig validators. In January 2024, a separate bug caused roughly 150 million $ONE to be erroneously minted and distributed to 79 wallets — an unintentional protocol error rather than a targeted attack. The 2026 incident is the first in which a deliberate, large-scale unauthorised mint has been confirmed.

Root Cause Analysis

An official post-mortem from the Harmony core team had not been published at the time of writing. Based on on-chain forensics reported by CryptoBriefing and community analysis, the exploit is described as an empty-block validation bypass — a class of consensus-layer vulnerability in which an attacker is able to submit blocks containing specially crafted (or absent) transaction content that causes the node's validation logic to skip or incorrectly execute the checks that govern supply-altering operations. We will update this section as authoritative details become available.

In a proof-of-stake network like Harmony, block production and validation are separated: a validator is chosen to propose a block, and other validators vote to accept it. The validation logic checks that the block's transactions are individually valid and that the aggregate state transitions they represent are consistent with the current chain state. An empty-block validation bypass exploits a gap in this logic — specifically, a condition in which a block that appears structurally valid by header checks alone is accepted without fully executing the transaction-level validation that would catch a supply manipulation.

The following illustrative reconstruction shows a simplified Harmony Go node validation pattern that could produce an empty-block bypass. This is not a verbatim reproduction of Harmony's source code; it is a representative example of the structural flaw class for educational purposes, and will be updated once an official post-mortem is published.

// VULNERABLE — block validation skips transaction execution for "empty" blocks
func (v *Validator) ValidateBlock(block *types.Block) error {
    // Header checks: hash, timestamp, proposer signature — all correct.
    if err := v.validateHeader(block.Header()); err != nil {
        return err
    }

    // Early return for blocks with no transactions — skips the
    // state-transition execution that would catch supply manipulation.
    if len(block.Transactions()) == 0 {
        return nil  // BUG: state-changing internal messages still execute
    }

    // Transaction-level validation (never reached for crafted empty blocks)
    return v.executeAndValidateTransactions(block)
}

// PATCHED — state transition validation runs regardless of transaction count
func (v *Validator) ValidateBlock(block *types.Block) error {
    if err := v.validateHeader(block.Header()); err != nil {
        return err
    }

    // Always execute and validate the full state transition,
    // including internal messages and supply-affecting operations,
    // even when the external transaction list is empty.
    if err := v.executeAndValidateTransactions(block); err != nil {
        return err
    }

    // Enforce supply cap as a post-execution invariant check.
    newSupply := v.stateDB.GetTotalSupply("ONE")
    if newSupply.GT(HardSupplyCap) {
        return ErrSupplyCapViolation
    }

    return nil
}

The pattern illustrates why a post-execution supply invariant check is a necessary defence-in-depth measure even after the primary bypass is patched. If the state database is queried for the total supply after every block execution — and the block is rejected if that supply exceeds the protocol's defined hard cap — then even a future bypass of the transaction-level validation cannot produce a supply expansion larger than the cap allows. This kind of independent invariant check is a standard practice in traditional financial systems and deserves wider adoption at the consensus layer of public blockchains.

It is worth noting that Harmony's June 2022 Horizon Bridge theft — attributed by the FBI to the Lazarus Group — also exploited a bypass of a critical security check, specifically the multisig threshold that was supposed to require majority consensus among bridge validators before releasing funds. Two events separated by four years, on the same network, both involving bypasses of controls that should have prevented unauthorised value transfers, suggest that Harmony's validation architecture has historically been constructed with insufficient redundancy at its most critical checkpoints.

Incident Response

Harmony's immediate response followed the established playbook for large-scale mint or bridge exploits: pause the most obvious exit route for stolen assets and request cooperation from centralised counterparties. Pausing the token bridge was the correct first action. The bridge is the pathway through which $ONE minted on Harmony can be converted to wrapped representations on external chains, where liquidity is sufficient to absorb large sales without immediately alerting the market to an ongoing incident.

The request to freeze assets at exchanges based on four identified attacker address clusters is a reasonable step, but its effectiveness depends heavily on timing. By the time freeze requests were issued, approximately 2.8 billion of the four billion minted tokens had already been routed through 409 wallets toward exchange deposit addresses. Centralised exchanges can freeze incoming deposits from flagged addresses and suspend withdrawals pending investigation, but they cannot recover assets already converted to other tokens or transferred out. The forensic tracing work that identified the 10,288-transfer movement pattern across 409 wallets was an important step in making those exchange requests actionable.

The longer-term fix requires a node-level patch deployed to the full validator set. Unlike a smart-contract upgrade, which can often be deployed unilaterally by a contract owner, a consensus-layer patch requires a coordinated upgrade of validator software across a sufficient fraction of the network to maintain block production continuity. Harmony's bridge suspension and the rollback plan together represent a bridge between the immediate response — limiting further damage — and the structural fix that makes normal operation safe to resume.

Lessons Learned

The most important lesson from this incident is structural rather than technical. Three significant security events on a single chain within three years — a $100 million bridge theft attributed to a nation-state hacking group, an erroneous minting bug, and now a deliberate large-scale unauthorised mint — indicate a systemic problem with how security controls are designed, audited, and maintained across Harmony's protocol stack. Each incident exploited a different bypass of a critical control, but all three share a common failure mode: a check that was supposed to prevent an unauthorised value transfer turned out to be circumventable under adversarial conditions.

For any proof-of-stake chain, the block validation logic that governs state transitions should be treated as the most security-critical code in the system. This means independent security audits at every protocol upgrade, adversarial fuzzing of block construction inputs with crafted or absent transaction payloads, and post-execution invariant checks on economically critical state variables — especially total token supply. An invariant check that runs after every block and rejects the block if total supply has exceeded a hard cap would have prevented this attack regardless of the specific bypass technique used.

The rollback debate that followed this attack highlights a tension at the heart of public blockchain design. Immutability is not merely a technical property — it is a social contract between the protocol and its users that says confirmed transactions are final. A rollback breaks that contract for every legitimate user whose transaction occurred during the attack window, not just for the attacker. The 2016 Ethereum DAO rollback produced Ethereum Classic as a permanent reminder that not everyone accepts this trade-off. For Harmony, the calculus is further complicated by the reality that approximately 2.8 billion of the minted tokens had already reached exchange deposit addresses by the time the rollback was being considered — meaning a rollback would impose costs on innocent users without recovering a majority of the stolen supply.

For exchanges and custodians listing proof-of-stake assets with active development teams, this incident is a reminder that governance-level decisions — including rollbacks — can alter the canonical chain state beneath assets already credited to user accounts. A deposit confirmation policy that pauses crediting during declared network incidents, regardless of on-chain confirmation count, provides meaningful protection against both double-spend attacks and rollback scenarios. It is a straightforward operational control that many exchanges have not yet implemented as a standard policy for assets on smaller, more actively governed chains.