Hyperlane
Hyperlane is the modular interoperability platform, empowering developers to build interchain applications, apps that can easily and securely communicate between blockchains.
PoC Required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Any governance voting result manipulation
Unauthorized minting of interchain assets, whether fungible or not
Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)
Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc.
Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Direct theft of any user NFTs, whether at-rest or in-motion, other than unclaimed royalties
Permanent freezing of funds
Permanent freezing of NFTs
Unauthorized minting of NFTs
Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)
Protocol insolvency
Out of scope
The following vulnerabilities are excluded from the rewards for this bug bounty program:
- Attacks requiring access to privileged addresses (governance, owner, etc)
- Vulnerabilities in components that exist in the codebase but are demonstrably unused or not integrated with production systems will be classified as invalid.
- Throttling or suppression of operations without loss of user and / or protocol funds
- Best practice critiques
- ‘Contract DDoS’
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers