Exodus Bug Bounty Program

Program Overview

Exodus Movement, Inc., founded in 2015, develops the Exodus Wallet, a beautifully designed, non-custodial multi-asset software wallet available on desktop, mobile, and browser platforms that supports over 100,000 asset pairs while keeping users' private keys encrypted and stored locally on their own devices.

For more information about Exodus, please visit https://www.exodus.com/.

Rewards

Exodus provides rewards in USDC on Ethereum, denominated in USD.

Rewards by Threat Level

Websites and Applications

Rewards by Asset

Reward Calculation for Critical Level Reports

For critical web/apps bugs, reports will be rewarded with Max Critical only if the impact leads to:

• A loss of funds involving an attack that does not require any user action
• Private key or private key generation leakage leading to unauthorized access to user funds

All other impacts that would be classified as Critical would be rewarded a flat amount of minimum reward as per the table above.

Reward Payment Terms

Payouts are handled by the Exodus team directly and are denominated in USD. However, payments are done in USDC on Ethereum.

The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.

Eligibility Criteria

Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:

• On OFAC's SDN list
• A contracted technical contributor who is being directly compensated by the project or directly compensated by a contracted organization providing technical services to the project
• A former contracted technical contributor who, for the past year from the date of the bug report submission, was directly compensated by the project or was compensated by a contracted organization to the project. In the case of the latter, the status of the organization's contract with the project is irrelevant.

KYC Requirement

Exodus will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:

• Full name
• Date of birth
• Proof of address (either a redacted bank statement with address or a recent utility bill)
• Copy of Passport or other Government issued ID

The submission of KYC information is a requirement for payout processing.

Proof of Concept (PoC) Requirements

A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.

Proof of concept is always required for all severities.

Responsible Publication

Exodus adheres to Category 2: Notice Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports.

Primacy of Impact vs Primacy of Rules

Exodus adheres to the Primacy of Impact for the following impacts:

• Website & Application — Critical

Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.

When submitting a report on Immunefi's dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.

If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.

All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program.

Public Disclosure of Known Issues

Bug reports covering previously-discovered bugs are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to "fix", necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk.

Known Issues:

• In-App web3 browser findings except sandbox bypassing affecting wallets directly.

Prohibited Activities

• Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
• Any testing with pricing oracles or third-party smart contracts
• Attempting phishing or other social engineering attacks against 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 that are executed against project assets
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty
• Any other actions prohibited by the Immunefi Rules

Feasibility Limitations

The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.

Immunefi has developed feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.