Hyperlane
Submit a BugProgram Overview
Hyperlane is the modular interoperability platform, empowering developers to build interchain applications, apps that can easily and securely communicate between blockchains.
For more information about Hyperlane, please visit https://www.hyperlane.xyz/.
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Critical and High Smart Contract bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.
Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 20 000. High smart contract vulnerabilities are capped at 10% of economic damage as well, with a minimum reward of USD 10 000.
Hyperlane requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed are Name and Identity Proof (Passport, / Driving License / National ID). The collection of this information will be done by the project team.
Payouts are handled by the Hyperlane team directly and are denominated in USD. However, payouts are done in USDC.
Smart Contract
- Critical
- Level
- USD $20,000 to USD $2,500,000
- Payout
- High
- Level
- USD $10,000 to USD $200,000
- Payout
- Medium
- Level
- USD $5,000
- Payout
- Low
- Level
- USD $2,000
- Payout
Websites and Applications
- Critical
- Level
- USD $20,000
- Payout
- High
- Level
- USD $10,000
- Payout
- Medium
- Level
- USD $5,000
- Payout
- Low
- Level
- USD $1,000
- Payout
Assets in scope
- Smart Contract - Arbitrum validatorAnnounceType
- Smart Contract - Arbitrum proxyAdminType
- Smart Contract - Arbitrum proxyType
- Smart Contract - Arbitrum implementationType
- Smart Contract - Arbitrum proxyType
- Smart Contract - Arbitrum implementationType
- Smart Contract - Arbitrum defaultIsmInterchainGasPaymasterType
- Smart Contract - Arbitrum multisigIsmType
- Smart Contract - Arbitrum create2FactoryType
- Smart Contract - Arbitrum interchainAccountRouterType
- Smart Contract - Arbitrum interchainQueryRouterType
- Smart Contract - Avalanche validatorAnnounceType
- Smart Contract - Avalanche proxyAdminType
- Smart Contract - Avalanche proxyType
- Smart Contract - Avalanche implementationType
- Smart Contract - Avalanche proxyType
- Smart Contract - Avalanche implementationType
- Smart Contract - Avalanche defaultIsmInterchainGasPaymasterType
- Smart Contract - Avalanche multisigIsmType
- Smart Contract - Avalanche create2FactoryType
- Smart Contract - Avalanche interchainAccountRouterType
- Smart Contract - Avalanche interchainQueryRouterType
- Smart Contract - Binance validatorAnnounceType
- Smart Contract - Binance proxyAdminType
- Smart Contract - Binance proxyType
- Smart Contract - Binance implementationType
- Smart Contract - Binance proxyType
- Smart Contract - Binance implementationType
- Smart Contract - Binance defaultIsmInterchainGasPaymasterType
- Smart Contract - Binance multisigIsmType
- Smart Contract - Binance create2FactoryType
- Smart Contract - Binance interchainAccountRouterType
- Smart Contract - Binance interchainQueryRouterType
- Smart Contract - Celo validatorAnnounceType
- Smart Contract - Celo proxyAdminType
- Smart Contract - Celo proxyType
- Smart Contract - Celo implementationType
- Smart Contract - Celo proxyType
- Smart Contract - Celo implementationType
- Smart Contract - Celo defaultIsmInterchainGasPaymasterType
- Smart Contract - Celo multisigIsmType
- Smart Contract - Celo create2FactoryType
- Smart Contract - Celo interchainAccountRouterType
- Smart Contract - Celo interchainQueryRouterType
- Smart Contract - Ethereum validatorAnnounceType
- Smart Contract - Ethereum proxyAdminType
- Smart Contract - Ethereum proxyType
- Smart Contract - Ethereum implementationType
- Smart Contract - Ethereum proxyType
- Smart Contract - Ethereum implementationType
- Smart Contract - Ethereum defaultIsmInterchainGasPaymasterType
- Smart Contract - Ethereum multisigIsmType
- Smart Contract - Ethereum create2FactoryType
- Smart Contract - Ethereum interchainAccountRouterType
- Smart Contract - Ethereum interchainQueryRouterType
- Smart Contract - Gnosis validatorAnnounceType
- Smart Contract - Gnosis proxyAdminType
- Smart Contract - Gnosis proxyType
- Smart Contract - Gnosis implementationType
- Smart Contract - Gnosis proxyType
- Smart Contract - Gnosis implementationType
- Smart Contract - Gnosis defaultIsmInterchainGasPaymasterType
- Smart Contract - Gnosis multisigIsmType
- Smart Contract - Gnosis create2FactoryType
- Smart Contract - Moonbeam validatorAnnounceType
- Smart Contract - Moonbeam proxyAdminType
- Smart Contract - Moonbeam proxyType
- Smart Contract - Moonbeam implementationType
- Smart Contract - Moonbeam proxyType
- Smart Contract - Moonbeam implementationType
- Smart Contract - Moonbeam defaultIsmInterchainGasPaymasterType
- Smart Contract - Moonbeam multisigIsmType
- Smart Contract - Moonbeam create2FactoryType
- Smart Contract - Optimism validatorAnnounceType
- Smart Contract - Optimism proxyAdminType
- Smart Contract - Optimism proxyType
- Smart Contract - Optimism implementationType
- Smart Contract - Optimism proxyType
- Smart Contract - Optimism implementationType
- Smart Contract - Optimism defaultIsmInterchainGasPaymasteType
- Smart Contract - Optimism multisigIsmType
- Smart Contract - Optimism create2FactoryType
- Smart Contract - Optimism interchainAccountRouterType
- Smart Contract - avalanche inbox Optimism interchainQueryRouterType
- Smart Contract - Polygon validatorAnnounceType
- Smart Contract - Polygon proxyAdminType
- Smart Contract - Polygon proxyType
- Smart Contract - Polygon implementationType
- Smart Contract - Polygon proxyType
- Smart Contract - Polygon proxyType
- Smart Contract - Polygon implementationType
- Smart Contract - Polygon defaultIsmInterchainGasPaymasterType
- Smart Contract - Polygon multisigIsmType
- Smart Contract - Polygon create2FactoryType
- Smart Contract - Polygon interchainAccountRouterType
- Smart Contract - Polygon interchainQueryRouterType
- Websites and Applications - Main Web AppType
All smart contracts of Hyperlane can be found at https://github.com/hyperlane-xyz. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
Though only the proxy contracts are listed as in-scope, current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy smart contract as the target.
If an impact can be caused to any other asset managed by Hyperlane that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. The vulnerability will then be evaluated by Hyperlane core contributors in good faith to determine where it would lie on the vulnerability scale.
Impacts in scope
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.
Smart Contract
- Any governance voting result manipulationCriticalImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Direct theft of any user NFTs, whether at-rest or in-motion, other than unclaimed royaltiesCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Permanent freezing of NFTsCriticalImpact
- Miner-extractable value (MEV)CriticalImpact
- Unauthorized minting of NFTsCriticalImpact
- Predictable or manipulable RNG that results in abuse of the principalCriticalImpact
- Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)CriticalImpact
- Protocol insolvencyCriticalImpact
- Unauthorized minting of interchain assets, whether fungible or notCriticalImpact
- Theft of unclaimed yieldHighImpact
- Theft of unclaimed royaltiesHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Permanent freezing of unclaimed royaltiesHighImpact
- Temporary freezing of funds for at least 60 minutesHighImpact
- Temporary freezing NFTs for at least 60 minutesHighImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumptionMediumImpact
- Smart contract fails to deliver promised returns, but doesn’t lose valueLowImpact
Websites and Applications
- Execute arbitrary system commandsCriticalImpact
- 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)CriticalImpact
- Taking down the application/websiteCriticalImpact
- Taking down the NFT URICriticalImpact
- 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.CriticalImpact
- Changing the NFT metadataCriticalImpact
- Subdomain takeover with already-connected wallet interactionCriticalImpact
- Direct theft of user fundsCriticalImpact
- Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactionsCriticalImpact
- Direct theft of user NFTsCriticalImpact
- Injection of malicious HTML or XSS through NFT metadataCriticalImpact
- Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.HighImpact
- Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.HighImpact
- Improperly disclosing confidential user information such as email address, phone number, physical address, etc.HighImpact
- Subdomain takeover without already-connected wallet interactionHighImpact
- Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as changing the first/last name of user, or en/disabling notificationMediumImpact
- Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site dataMediumImpact
- Redirecting users to malicious websites (Open Redirect)MediumImpact
- Changing details of other users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction such as iframing leading to modifying the backend/browser state (demonstrate impact with PoC)LowImpact
- Any impact involving a publicly released CVE without a working PoCLowImpact
- Taking over broken or expired outgoing links such as social media handles, etc.LowImpact
- Temporarily disabling user to access target site, such as locking up the victim from login, cookie bombing, etc.LowImpact
Out of Scope & Rules
The following vulnerabilities are excluded from the rewards for this bug bounty program:
- Attacks that the reporter has already exploited themselves, leading to damage
- Attacks requiring access to leaked keys/credentials
- Attacks requiring access to privileged addresses (governance, strategist)
Smart Contracts and Blockchain
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
- Centralization risks
- ‘Contract DDoS’
Websites and Apps
- Theoretical vulnerabilities without any proof or demonstration
- DMARC email issues
- Attacks requiring physical access to the victim device
- Attacks requiring access to the local network of the victim
- Reflected plain text injection ex: url parameters, path, etc.
- This does not exclude reflected HTML injection with or without javascript
- This does not exclude persistent plain text injection
- Self-XSS
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (ex: logout CSRF)
- Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
- Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used only to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- DDoS vulnerabilities
- Feature requests
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
- Vulnerabilities primarily caused by browser/plugin defects
- Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
- Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass
The following activities are prohibited by this bug bounty program:
- Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
- Any testing with pricing oracles or third party smart contracts
- Attempting phishing or other social engineering attacks against our employees and/or customers
- Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Any denial of service attacks
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty