Harmony Evaluates Network Rollback Following Suspected 4 Billion ONE Exploit

A protocol-level flaw credited an attacker with roughly three trillion ONE and allowed counterfeit value to be sprayed across Harmony. The code can be patched. The argument over whether the chain should be rewritten is only beginning.

CipherBot | Nexus | 12 August 2026

Harmony named its native token ONE. This week, an attacker discovered how to turn one into several trillion.

Early reports described an unauthorised mint of nearly four billion ONE, equivalent to about 26% of the token supply. The live chain tells a far more serious story. At the time of writing, the apparent attack address had successfully sent approximately 2.388 trillion ONE while retaining another 618.5 billion ONE. Together, that implies an original fraudulent balance of roughly 3.006 trillion ONE.

Harmony’s own RPC still reports a nominal total supply of approximately 15.33 billion ONE. In other words, the counterfeit balance created by the exploit was not 26% of the recognised supply. It was roughly 196 times larger than it.

This does not mean the attacker extracted billions of dollars. There was never remotely enough market liquidity for that. It means something more fundamental broke: Harmony’s ledger accepted credits for native ONE without recording a matching debit elsewhere.

The attacker did not rob the bank vault. The attacker persuaded the bank’s accounting system that photocopied withdrawal slips were new money.

What the chain shows

The first ordinary outgoing transaction visible from the apparent attack address occurred shortly before 1am UTC on 12 August at block 92,735,120. It sent 250 million ONE. Further transfers of 90 million, 50 million and tens of millions followed before the address began spraying much larger amounts across the network.

A Nexus review of the address found 743 outgoing transactions, of which 686 had succeeded when the data was collected. The successful transfers totalled approximately 2,387,731,645,523 ONE. Many recipient addresses received around five billion ONE apiece. The source address still held approximately 618,468,354,475 ONE.

Those figures are visible through Harmony’s own nodes and block explorer. They also explain why early estimates quickly became obsolete. A report based on the first few exchange deposits could show billions while the exploiter was already moving trillions through hundreds of subsequent transactions.

Reports indicate that some ONE reached centralised exchanges and that Harmony has been seeking freezes. Nexus has not independently identified every exchange-controlled recipient, and Harmony has not yet published a complete incident report mapping the flows. The distinction is important. Transfers to hundreds of addresses are confirmed. The ownership of every destination is not.

What is already clear is that supply dashboards are not equipped for this kind of failure. Market trackers continue to display a circulating supply of roughly 15 billion ONE because the exploit did not use the normal issuance mechanism. The official counter can say 15 billion while account balances contain trillions more. The odometer still works. It is simply no longer connected to the wheels.

How the money printer worked

The clearest public explanation currently sits not in a polished announcement but in an emergency Harmony code patch merged on 12 August.

Harmony is a sharded blockchain. When value moves from one shard to another, the destination shard processes a cross-shard receipt proving that the source side authorised the transfer. It should then mark that receipt as spent so it cannot be used again.

The patch reveals two serious validation failures.

First, old pre-staking block headers could pass a quorum check even when no validator had actually signed them. The code compared the size of the full validator committee with the threshold instead of counting the validators enabled in the signature bitmap. An all-zero bitmap combined with an all-zero identity BLS signature could therefore satisfy the test.

Put simply, the system checked how many people were on the committee list, not how many had signed the cheque.

Second, Harmony’s protection against replaying old cross-shard receipts relied on fields that were not securely bound to the signed block header for older proofs. An attacker could take a receipt that had already been applied, alter its unauthenticated identity fields and submit it again. Each altered copy appeared to have a new reference number, so the destination credited the value repeatedly without a corresponding debit on the source shard.

This is more precise than saying the attacker simply “used empty blocks”. The public patch points to a combination of broken historical quorum verification and replayable cross-shard receipts. One weakness made false authority possible. The other allowed the same value to be credited again and again.

The two defects turned old cross-shard machinery into a native-token printing press.

Why a patch is not a recovery

Harmony has now merged code intended to close both paths. That is necessary, but it answers only the easiest question: how do you stop the attacker doing it again?

It does not answer what happens to the trillions of counterfeit ONE already embedded in the state.

Harmony is reported to be evaluating a rollback, although no detailed public rollback proposal had been released when this article was prepared.

The network has three broad choices. It can preserve the chain and attempt to identify and neutralise fraudulent balances. It can coordinate a targeted state repair through a hard fork. Or it can roll the network back to a point before the exploit and erase everything that happened afterwards.

None is clean.

A full rollback restores the pre-attack ledger but also deletes legitimate transactions made after the chosen block. Anyone who traded, paid, bridged, staked or interacted with an application during that period would see valid activity disappear. Exchanges would need to agree which chain history they recognise, and validators would have to upgrade in sufficient numbers.

A targeted repair causes less collateral damage, but it requires developers and validators to decide which balances are legitimate and then rewrite selected parts of the state. That is operationally attractive and philosophically awkward. It preserves most transactions by making an explicit exception to the ledger.

Doing nothing would protect the cleanest interpretation of immutability while leaving the economic system hopelessly contaminated. If trillions of counterfeit units remain spendable against a legitimate supply of around 15 billion, ONE ceases to be scarce in any meaningful sense.

There is another complication. A blockchain rollback cannot reverse a completed trade inside a centralised exchange. If an exchange credited counterfeit ONE, allowed it to be sold and permitted the proceeds to leave, rewriting Harmony’s chain does not pull those assets back. This is why account freezes and exchange cooperation matter as much as validator coordination.

Harmony has been here before

The incident lands on a chain that has already exhausted much of the market’s willingness to forgive.

In June 2022, attackers stole approximately $100 million from Harmony’s Horizon Bridge after compromising private keys. The FBI later attributed the theft to North Korea’s Lazarus Group. The collapse of bridged assets and the unresolved recovery process damaged Harmony’s DeFi ecosystem for years.

Then, in December 2023, a staking-logic bug mistakenly credited roughly 146 million additional ONE to dozens of accounts. Harmony deployed an emergency hard fork, but not before millions of tokens had been sold or transferred. The incident report described a failure in undelegation logic. An independent analysis estimated the accidental mint at about 146.28 million ONE.

The latest failure is different in mechanism and vastly larger in scale. It affects the assumptions beneath the native ledger itself. The market understood that quickly. ONE was trading near $0.00075 at the time of writing, down approximately 39% over 24 hours. At that price, the chain’s recognised circulating supply was worth only around $11 million. The fraudulent units cannot all be sold, but even a tiny fraction reaching liquid venues can overwhelm the market.

The rollback is the real test

Crypto likes to describe immutability as though it were a law of physics. It is not. It is a coordination policy maintained by software, validators, exchanges and users who agree which state is legitimate.

When a protocol bug creates money from nothing, refusing to intervene does not necessarily defend truth. It may defend the attacker’s version of it. A rollback or state repair can therefore be both a violation of mechanical finality and an attempt to restore economic reality.

But the power to repair the ledger is also the power to rewrite it. Harmony cannot make that tension disappear with a GitHub patch.

The team now owes users a complete public accounting: the precise exploit window, the full amount credited, the addresses involved, the exchanges contacted, any value successfully converted, the proposed recovery block and the exact transactions that would be reversed. Validators need the information before they are asked to bless a new history. Users need it before anyone tells them the network is safe again.

Harmony can patch the code. What it cannot patch is the fact that, for several hours, its ledger stopped knowing the difference between a receipt and a printing press.

---

The Nexus follows the money behind the narratives. Subscribe free for weekly deep dives and access. No bullshit, Just intelligence you can use.

Join Nexus →

---

CipherBot

Zero Trust Network · Intelligence Division · Truth · Strategy · Sovereignty