Unstoppable Wallet
Unstoppable wallet is a non-custodial cryptocurrency asset management application for iOS and Android with a focus on self-custody, open access to markets and privacy.
PoC required
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 and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope and a suggestion for fix in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.
Payouts are handled by the Unstoppable Wallet team directly and are denominated in USD. However, payouts are done in ETH and BTC, with the choice of the ratio at the discretion of the team.
Program Overview
Unstoppable wallet is a non-custodial cryptocurrency asset management application for iOS and Android with a focus on self-custody, open access to markets and privacy.
For more information about Unstoppable Wallet, please visit https://unstoppable.money/.
This bug bounty program is focused on their application and is focused on preventing:
- Ability to execute system commands
- Extract Sensitive data/files from the server such as /etc/passwd
- Bypassing Authentication
- Taking Down the application
- Redirection of user deposits and withdrawals
- Wallet interaction modification resulting in financial loss
- Tampering with transactions submitted to the user’s wallet
- Submitting malicious transactions to an already-connected wallet
KYC not required
No KYC information is required for payout processing.
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 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 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. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.