Hyperbridge cross-chain bridge attacked: 1 billion DOT minted out of thin air, attacker only profits $230k

On April 13, 2026, the blockchain security firm CertiK detected a vulnerability attack on the Hyperbridge cross-chain gateway contract. The attacker forged cross-chain messages to tamper with the administrator permissions of the Polkadot (DOT) token contract on Ethereum, illegally minted 1 billion bridged DOT tokens, and sold them all, ultimately profiting about 108.2 ETH, equivalent to approximately $237k. This so-called “massive heist” with a nominal value exceeding $1 billion was rendered illusory due to liquidity shortages, but it re-focused industry attention on the long-standing security vulnerabilities of cross-chain bridges.

How the MMR Proof Replay Vulnerability Was Triggered

What is the technical root cause of this attack? BlockSec Phalcon characterized this vulnerability as an MMR (Merkle Mountain Range) proof replay flaw. Hyperbridge’s HandlerV1 contract, in its replay protection mechanism, only verifies whether the hash of the request commitment has been used before, but the proof verification process does not bind the submitted request payload to the proof being validated.

This logical gap allows an attacker to replay a previously accepted valid proof from the system, pair it with a newly constructed malicious request, and execute the ChangeAssetAdmin operation via the TokenGateway.onAccept() path, transferring the admin and minting permissions of the wrapped DOT contract on Ethereum to an address under their control. An update note released by Hyperbridge further confirms that the root cause lies in the VerifyProof() function, which lacks input validation for leaf_index < leafCount, enabling the attacker to forge Merkle proofs. Essentially, this is a classic “replay attack + privilege escalation” combined vulnerability—attackers did not break cryptographic primitives but exploited the disjointed verification logic across modules.

Why Only $237k Was Cashed Out from 1 Billion DOT

The most ironic data point in this attack is the huge disparity between 1 billion tokens and the $237k cashout. According to Lookonchain data, before the sale, the bridged DOT was priced at about $1.22, with a maximum theoretical arbitrage of over $1.2 billion.

However, the on-chain liquidity of bridged DOT on Ethereum was extremely limited. The attacker used Odos Router and Uniswap V4 liquidity pools to concentrate and sell the 1 billion tokens, instantly crashing the price from $1.22 to near zero. The 1 billion minted tokens represented about 2,805 times the then-reported circulating supply of approximately 356k DOT. This massive supply shock overwhelmed the shallow liquidity pools, causing severe slippage and rendering most of the newly minted tokens essentially worthless. The attacker could create tokens but could not create buyers or liquidity.

The Security Boundary Between Bridged Assets and Native Assets

A key fact to clarify is: the attack targeted the bridged DOT token contract deployed on Ethereum, not the native Polkadot main chain. Polkadot’s official statement clarified that this vulnerability only affected DOT bridged to Ethereum via Hyperbridge; the native DOT tokens and other assets within the Polkadot ecosystem were not directly compromised. Hyperbridge is a third-party cross-chain gateway project developed by Polytope Labs, not a core infrastructure built and maintained by Polkadot.

This distinction reveals a core paradox in cross-chain bridge security: the smart contracts managing bridged assets are independently deployed on target chains, and their security audits and monitoring may differ from those of the native chain. Attackers do not need to touch the consensus layer of the main chain; they can cause large-scale damage on the target chain by exploiting a single vulnerability in the bridge contract. Users holding bridged assets bear risks not only from the underlying main chain but also from the security of the bridge infrastructure itself.

What Trends Will Cross-Chain Bridge Attacks Show in 2026?

The Hyperbridge attack is not an isolated incident in 2026. Broader industry data shows that in the first quarter of 2026, total losses from DeFi hacking attacks amounted to about $168 million. Although this is a significant decrease from approximately $1.58 billion in the same period in 2025, structural risks persist. In February 2026, CrossCurve’s cross-chain bridge lost about $3 million due to smart contract vulnerabilities; in the same month, ioTube bridge suffered over $4.4 million in losses after a private key leak of the Ethereum side validator contract. Cross-chain bridges account for over 60% of major DeFi security incidents historically and remain one of the most targeted attack vectors for hackers.

Sherlock, a security research organization, released a cross-chain security report in early 2026, noting that current cross-chain attacks follow predictable patterns: trust assumptions encoded as deterministic guarantees, authentication failures at message boundaries, and systems granting all permissions via a single execution path. The Hyperbridge incident perfectly fits this description—its smart contract assumed that the MMR proof verification was securely bound to the request, but logical gaps in the code nullified this assumption.

Is Low Liquidity a “Shield” or a Greater Hidden Risk?

In this attack, low liquidity objectively served as a “shield,” limiting the attacker’s profit to about $237k. If the same vulnerability had occurred on a bridge with deeper liquidity or higher-value assets, the losses could have scaled exponentially. This “limited loss but extremely high risk” paradox is precisely the most challenging issue in cross-chain security—the industry tends to be lulled into complacency by single, limited incidents, underestimating the systemic threat posed by such vulnerabilities.

On the other hand, the insufficient liquidity of bridged assets is itself a sign of market health issues. The bridged DOT on Ethereum has a circulating supply of only about 356k tokens, with very shallow liquidity pools. This means that even without attacks, large transactions cause severe slippage, impairing normal asset usability. The low liquidity “saved” Polkadot in this case but exposed the deep fragility of the cross-chain interoperability layer—bridged assets lack both sufficient market depth and security redundancy.

What Is the Core Contradiction in Cross-Chain Security?

The core of the cross-chain bridge security dilemma is the fundamental contradiction of “trust migration.” Cross-chain bridges are essentially “security adapters”—they translate finality, membership, and authorization information from one chain into trusted instructions in another execution environment. Any logical gap in this translation process can be exploited by attackers.

The industry faces multiple challenges: first, the code complexity of cross-chain bridges far exceeds that of single-chain smart contracts, involving oracles, relayers, validators, and other components working in concert; second, many projects prioritize “getting online quickly” over “thorough understanding,” embedding security risks into their technical decisions. Moreover, formal verification and mathematically provable security methods are not yet standard industry practice, and third-party audits vary greatly in depth and frequency.

What Should the Future of Cross-Chain Security Look Like?

From this incident, several clear directional insights can be drawn. First, verification mechanisms must ensure full-chain binding of “request-proof” pairs, eliminating logical gaps. Second, cross-chain protocols should adopt minimal permission management and multi-layer verification as design principles, not afterthought patches. Third, the industry needs to establish more transparent trust models—users should clearly understand the security assumptions and risk boundaries when using cross-chain bridges. Finally, security audits should evolve toward formal verification and continuous monitoring, upgrading from “one-time checks” to “full lifecycle protection.”

As a critical infrastructure connecting multiple chains, the security of cross-chain bridges will directly influence the future development of Web3 interoperability. The Hyperbridge incident’s value lies not in the $237k loss but in its almost absurd revelation of an undeniable truth in cross-chain security: the destructive power of vulnerabilities often depends not on the attacker’s ambition but on the system’s inherent respect for security assumptions.

Summary

The Hyperbridge cross-chain bridge MMR proof replay vulnerability allowed an attacker to mint 1 billion bridged DOT tokens, but due to severe liquidity shortages on Ethereum, only about $237,000 was cashed out. The incident did not affect the Polkadot native main chain but highlighted the systemic fragility of bridge assets in terms of security auditing and liquidity depth. Cross-chain bridge attacks continued into 2026, and the industry must systematically improve security standards in verification binding, minimal permission management, and formal security verification.

Frequently Asked Questions

Q: Will the 1 billion DOT minted in the Hyperbridge attack affect the total supply of Polkadot native DOT?

A: No. The attacker minted the bridged version of DOT deployed on Ethereum, which is a wrapped asset, not the native DOT on Polkadot. The total supply and security of the native DOT remain unaffected.

Q: Why did the attacker only profit $237,000 instead of the nominal value of 1 billion DOT?

A: The core reason is the extremely limited on-chain liquidity of bridged DOT on Ethereum. When the attacker sold the 1 billion tokens, severe slippage caused the price to plummet from $1.22 to near zero, making most of the newly minted tokens effectively unsellable.

Q: What is the MMR proof replay vulnerability?

A: MMR (Merkle Mountain Range) is a variant of Merkle trees, often used for light client verification in blockchains. The core of this vulnerability is that Hyperbridge’s HandlerV1 contract’s verification process lacked binding between the proof and the request, allowing attackers to replay valid historical proofs combined with forged new requests to bypass validation and gain admin privileges.

Q: Why are cross-chain bridges frequent targets of attacks?

A: Cross-chain bridges hold token contract management permissions, and if their verification mechanisms are compromised, attackers can mint unlimited tokens or steal assets. They involve multiple smart contracts and off-chain components across different chains, creating a larger attack surface than single-chain protocols, making them highly attractive targets.

Q: How should users holding bridged DOT assess their risks?

A: Users should recognize that risks come not only from the underlying main chain but also from the security of the bridge’s smart contracts. It is recommended to review the bridge’s security audit history, liquidity pool depth, and past security incidents before participating in liquidity provision or holding bridged assets.