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.
Triaged by Immunefi
PoC Required
KYC required
Arbitration enabled
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Price manipulation results in the alteration of the perceived value of cryptocurrencies by either tampering with price feeds or tampering marketplace prices to acquire items at lower costs.
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)
Direct theft of user funds
Improperly disclosing confidential user information without any user interaction such as: Email address, Phone number, SSN, DOB
Subdomain takeover with already-connected wallet interaction
Taking state-modifying authenticated actions on behalf of other users without any interaction by that user, such as: Changing sensitive information, Deleting wallet, Displaying an attacker-controlled wallet address on user accounts as the designated deposit wallet
Injecting/modifying the static content on the target application with Javascript without unrealistic user interaction such as: Initiating malicious transaction, Stealing secret phrase, Client side RCE, Retrieving sensitive information such as user’s email address, SSN
Changing sensitive details of other users (including modifying browser local storage) with up to one click of user interaction
Sitewide disruption of core services
Subdomain takeover without already-connected wallet interaction
Injecting/modifying the static content on the target application without Javascript such as: Stored/Reflected HTML, Loading external site data, Redirecting to malicious website (Without requiring user to manually enter website on the in-app browser)
Out of scope
"support.exodus.com" is out of scope for the testing.
To request permission, please email [email protected] and mention the details of your test including what endpoint(s) you will be hitting, what type of scan/attack/etc you would like to try, and what you're trying to achieve. We will respond within 2 working days, ideally less to your request. As long as it is reasonably well thought out and we don't see a risk on our end, we will approve the request.
Web & App specific
- Theoretical impacts without any proof or demonstration
- Impacts involving attacks requiring physical access to the victim device
- Impacts involving attacks requiring access to the local network of the victim
- Reflected plain text injection (e.g. url parameters, path, etc.)
- This does not exclude reflected HTML injection with or without JavaScript
- This does not exclude persistent plain text injection
- Any impacts involving self-XSS
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (e.g. logout CSRF)
- Impacts related to 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
- Impacts causing only the enumeration or confirmation of the existence of users or tenants
- Impacts caused by vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- Impacts that only require DDoS
- UX and UI impacts that do not materially disrupt use of the platform
- Impacts primarily caused by browser/plugin defects
- Leakage of non sensitive API keys (e.g. Etherscan, Infura, Alchemy, etc.)
- Any vulnerability exploit requiring browser bugs for exploitation (e.g. CSP bypass)
- SPF/DMARC misconfigured records)
- Missing HTTP Headers without demonstrated impact
- Automated scanner reports without demonstrated impact
- UI/UX best practice recommendations
- Non-future-proof NFT rendering
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