All code of Mountain Protocol can be found at [https://github.com/orgs/mountainprotocol/repositories.](https://github.com/orgs/mountainprotocol/repositories) Documentation for the assets provided in the table can be found at [https://docs.mountainprotocol.com/. ](https://docs.mountainprotocol.com/)

Unless explicitly listed, only pages of the web/app assets in addition to the direct link are considered in-scope of the bug bounty program. Other subdomains are not considered as in-scope. However, for subdomain takeovers that lead to an impact on the in-scope asset, please refer to our page about [Reported Subdomain Takeovers](https://immunefisupport.zendesk.com/hc/en-us/articles/14352199704593-Reported-Subdomain-Takeovers).


Mountain Protocol is the issuer of the first regulated and permissionless yield-bearing stablecoin: USDM. Fully backed by US Treasuries, USDM allows stablecoin holders to continue the experience they know with stablecoins like USDT/USDC while earning rewards at or about the “risk-free” yield that the collateral is generating.

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Protocol insolvency

Unauthorized interactions with the smart contract that could benefit an attacker or damage Mountain Protocol or its users, including any action behind the access control mechanism such as minting, burning, etc.

Execute arbitrary system commands

Retrieve sensitive data/files from a running server such as: /etc/shadow, database passwords, 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.

Direct theft of user funds

Unauthorized transfer of funds from custody setup to outside EOAs. Demonstration required.

Theft of unclaimed yield (does not include cases where USDM is used in other protocols)

Permanent freezing of unclaimed yield

Temporary freezing of funds (more than 24hs)

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.

Taking down the application/website

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

Injecting/modifying the static content on the target application without Javascript (Reflected) such as: Reflected HTML injection, Loading external site data

Redirecting users to malicious websites (Open Redirect)

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. 

Vulnerabilities are limited to __10%__ of economic damage, taking into account funds at risk and reputation at the team's discretion. However, each severity has a defined maximum and minimum (eg, 50k and 100k for critical).

__Repeatable Attack Limitations__

In cases of repeatable attacks for smart contract bugs, only the first attack will be counted, regardless of whether the smart contract is upgradable, pausable, or killable.

__Restrictions on Security Researcher Eligibility__

Security researchers who fall under any of the following are ineligible for a reward
- OFAC sanctioned
- Sanctioned Persons
- Politically Exposed Persons

__Public Disclosure of Known Issues__

Bug reports covering previously-discovered bugs acknowledged below are not eligible for any reward through the bug bounty program. 
- Centralization risks (upgrade, blocklisting, reward multiplier, access control, pausing, mint, burn and other functions expected to be done centrally). Access to these functions by other than Mountain Protocol is part of the bounty program.
- Tokenomics design risks

__Previous Audits__

Mountain Protocol has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
- [https://github.com/mountainprotocol/audits](https://github.com/mountainprotocol/audits)

__Proof of Concept (PoC) Requirements__

A PoC is required for the following severity levels:
- Smart Contract - Critical
- Smart Contract - High
- Smart Contract - Medium
- Web/App - Critical
- Web/App - High
- Web/App - Medium

All PoCs submitted must comply with the Immunefi-wide [PoC Guidelines and Rules.](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules) Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

__Other Terms and Information__

- This bug bounty program will have a hard cap of USDC 100 000. In the event that multiple bug reports are submitted that exceed this amount, the rewards will be provided on a first come first served basis.

__Reward Payment Terms__

Payouts are handled by the Mountain Protocol team directly and are denominated in USD. However, payments are done in USDC.  
