Wormhole
DAMASCUSBridge / Messaging · Multi-chain · $1B+ TVL · 10 contracts
Public risk assessment — scores are produced with the same methodology as monitored protocols
Security Profile
75
80
85
70
72
68
50
78
62
75
96
75
80
85
70
72
68
50
78
62
75
96
Audit History
Bug Bounty Program
Assessment
Dominant cross-chain bridge, connects 30+ chains. $320M exploit (2022) is the defining event - rebuilt with improved security but historical scar permanently impacts D6/D7/D10. Post-exploit improvements are real.
Dimension Breakdown
How scores work →- 19-guardian validator set (improved from 13 post-exploit)
- Guardian key management remains centralized risk
- Rate limiting and governor contracts added post-exploit
- Threshold signature scheme requires 13/19 consensus
- Token bridge with wrapped asset model
- Relayer fee economics for cross-chain delivery
- No flash mint surface in bridge contracts
- Portal wrapped asset backed 1:1 by locked collateral
- VAA (Verifiable Action Approval) verification model
- Guardian attestation replaces traditional oracle
- No external price feed dependency in core
- Verification occurs on destination chain
- Live since August 2021 (57 months)
- $320M exploit February 2022 (Guardian key compromise on Solana)
- Significant rebuild and security improvements post-exploit
- Z-factor: 0.897 from launch, but exploit is 39 months old
- No validated findings in BlackHart tracker
- D7 = 100 (clean protocol per tracker reconciliation)
- No validated adversarial findings — score set to neutral baseline
- Connects 30+ blockchains with different security models
- Each chain integration adds unique attack surface
- NTT (Native Token Transfers) adds new composition
- Relayer network introduces liveness dependencies
- Wormhole Foundation controls upgrade authority
- Guardian set selection is permissioned
- W token governance launching but limited scope
- Upgrade process requires guardian consensus
- $320M bridge exploit is defining cross-chain risk event
- Guardian key compromise class is bridge-specific
- Message verification trust model across heterogeneous chains
- Rate limiting added as defense-in-depth post-exploit
- Dedicated security team formed post-exploit
- Guardian operator monitoring and rotation procedures
- Improved incident response from lessons learned
- Multi-chain deployment complexity remains operational risk
- Appears in 1 cross-protocol cascade chain(s)
- Failure cascades to 2 downstream protocol(s)
- Member of 1 dependency cluster(s)
- Score: 96/100 (higher = more isolated from systemic risk)
- Source: cross_protocol_composition.json dependency analysis
- Multi-language: Rust (Solana), Solidity (EVM), Move (Aptos/Sui)
- Complex cross-chain SDK and relayer infrastructure
- Verified contracts across all supported chains
- Dependency complexity from multi-chain support
Risk Drivers
Primary risk factors driving this score, ordered by severity.
Adversarial Risk Signals
Observable security posture indicators. These signals reflect publicly verifiable information and responsible disclosure outcomes. No specific vulnerability details are exposed.
Score History & Verification
Score provenance tracking begins with the next reassessment.
On-Chain Data
- Protocol Slug
- "wormhole"
- Oracle
- BRORegistry (Base)
- Evidence
- IPFS (pinned)
- Staleness Threshold
- 24 hours
registry.getScore("wormhole")Reduce exploitable risk
BlackHart Monitoring provides continuous adversarial analysis, vulnerability detection, remediation support, and verified reassessment when your risk posture improves.