Bridge Incident Registry
Support
Menu
Bridge entity

Hyperbridge

Hyperbridge is a cross-chain interoperability protocol. On April 13, 2026, a forged Merkle Mountain Range proof was accepted by its verifier and used to extract funds from the shared Token Gateway settlement layer. Hyperbridge paused bridging, patched and audited the verification stack, and relaunched in June with a redesigned architecture that deprecated the shared TokenGateway model while keeping the Hyperbridge protocol active.

activereviewedcurrent

Bridge facts

Canonical name
Hyperbridge
Type
Interoperability Protocol
Status
Active
Confidence
High
Primary chains
Ethereum, Base, BNB Chain, Arbitrum, Unknown
Primary assets
Unknown
Operator
Polytope Labs
Ecosystem
Hyperbridge
Launch date
Unknown
End date
Unknown
Terminal reason
Not applicable / unknown
Last reviewed
2026-09-03
Last verified
2026-09-03

Incident cases

  • Hyperbridge Token Gateway 2026 MMR verifier exploit2026-04-13

    An attacker submitted a forged Merkle Mountain Range proof containing an out-of-bounds leaf index that the verifier accepted. Downstream handlers treated the forged leaf as a valid Hyperbridge message and funds were extracted from Token Gateway. Hyperbridge paused bridging, patched and audited the stack, and later relaunched with a redesigned architecture.

    Exploitover $2 millionUnresolved

Evidence records

Official URL status

Official URL recorded as live_verified: https://blog.hyperbridge.network/april-13-post-mortem/
Independent incident archive

Help maintain bridge history

Support incident linkage, lifecycle updates, evidence preservation, broken-link replacement, and corrections.

Support BIR
Record maintenance

Report a correction

Report missing evidence, incorrect dates, outcome changes, recovery details, reimbursement status, or broken links. GitHub Issues are preferred for structured review; the Google Form is available if you do not use GitHub.

Open GitHub Issues →Use Google Form →