Harmony Hack

TOTAL LOST $300K
Low Other

Summarize with AI

Affected Chain 2026 Incident surface
Recovered - No recovery reported
All-Time Rank #1161 By amount stolen
Protocol Type MEV Target category

Incident Overview

On August 12, 2026, Layer-1 blockchain Harmony Protocol suffered a major protocol-level security incident when an attacker exploited an "empty blocks" vulnerability to fraudulently mint approximately 4 billion ONE tokens representing roughly 26% of the token's total circulating supply and causing the price of ONE to crash between 26% and 34%.

The exploit targeted a consensus or state-update bug involving empty blocks, allowing the attacker to mint ~4 billion ONE tokens out of thin air while bypassing standard protocol reporting endpoints (leaving totalSupply metrics temporarily unchanged). The attacker rapidly transferred approximately 2.8 billion ONE (~97% of the fraudulently created tokens) directly into centralized crypto exchanges for liquidation, leaving only around 115 million ONE in on-chain addresses. In response, Harmony requested exchanges to freeze funds from four identified attacker wallet addresses while the core team began developing a software patch and evaluating blockchain rollback options.

Key Attacker Addresses:

one1uap8dx2z0qsjxqthm5flgcxkeepsz3gsrghnfn (0xe7427699…014510)

one17u300a40ll5wphd8kj5hktryhdjq3ml9f4phy4

(0xf722f7f6…08efe5)

Incident Report

Protocol / Project Harmony
Date of Incident
Attack Technique Other
Classification Other

Protocol Information

Protocol Type MEV
Official Website www.harmony.one/
Protocol Twitter/X @harmonyprotocol
Team Anonymous
Source Code Unverified

Market Context at Time of Hack

Token Price at Hack $0.00117598
Market Cap at Hack $17.5M
% of Market Cap Stolen 1.72%
Token Categories
Smart Contract Platform Layer 1 (L1) Harmony Ecosystem Animoca Brands Portfolio Binance Launchpad YZi Labs (Prev. Binance Labs) Portfolio Made in USA

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of other and Solidity and EVM internals
Capital Required Seed capital to cover gas and initial position setup
On-Chain Access Ability to interact with smart contracts and deploy a custom exploit contract
Protocol Analysis Identification of the exploitable vulnerability in Harmony's contract logic - root cause: other
Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block
Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely, with a thorough Other audit checklist and test coverage

If you're auditing a protocol with similar architecture to Harmony, these are the critical security checks that could have prevented this incident (August 2026).

  • Verify all logic paths related to Other are guarded by proper access controls and input validation
  • Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Sources & References

Learn to Prevent the Next Harmony

The Harmony hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Recreate exploit patterns safely Free Trial