Arbitrum interchainGasPaymaster implementation

Arbitrum staticMerkleRootMultisigIsmFactory

Arbitrum staticMessageIdMultisigIsmFactory

Avalanche interchainGasPaymaster implementation

Avalanche staticMerkleRootMultisigIsmFactory

Avalanche staticMessageIdMultisigIsmFactory

Binance interchainGasPaymaster implementation

Binance staticMerkleRootMultisigIsmFactory

Binance staticMessageIdMultisigIsmFactory

All smart contracts of Hyperlane can be found at [https://github.com/hyperlane-xyz](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.

Hyperlane is the modular interoperability platform, empowering developers to build interchain applications, apps that can easily and securely communicate between blockchains. 

Any governance voting result manipulation

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

Miner-extractable value (MEV)

Unauthorized minting of NFTs

Predictable or manipulable RNG that results in abuse of the principal

Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)

Protocol insolvency

Unauthorized minting of interchain assets, whether fungible or not

Execute arbitrary system commands

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 down the application/website

Taking down the NFT URI

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.

Changing the NFT metadata

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions

Direct theft of user NFTs

Injection of malicious HTML or XSS through NFT metadata

Theft of unclaimed yield

Theft of unclaimed royalties

Permanent freezing of unclaimed yield

Permanent freezing of unclaimed royalties

Temporary freezing of funds for at least 60 minutes

Temporary freezing NFTs for at least 60 minutes

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.

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.

Improperly disclosing confidential user information such as email address, phone number, physical address, etc.

Smart contract unable to operate due to lack of token funds

Block stuffing for profit

Unbounded gas consumption

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 notification

Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site data

Redirecting users to malicious websites (Open Redirect)

Subdomain takeover without already-connected wallet interaction

Smart contract fails to deliver promised returns, but doesn’t lose value

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

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)

Any impact involving a publicly released CVE without a working PoC

Taking over broken or expired outgoing links such as social media handles, etc.

Temporarily disabling user to access target site, such as locking up the victim from login, cookie bombing, etc.

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/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__.

Hyperlane

Resources & Documentation