1inch - Wallet

These impacts are out of scope for this bug bounty program.

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 (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
• 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

Websites and Apps

• 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
• Impacts that only require DDoS
• UX and UI impacts that do not materially disrupt use of the platform
• Leakage of non sensitive API keys (e.g. Etherscan, Infura, Alchemy, etc.)
• Automated scanner reports without demonstrated impact
• UI/UX best practice recommendations
• Vulnerabilities requiring a rooted or jailbroken device, unless the impact occurs on a non-rooted device through the rooted attacker's actions
• Lack of binary obfuscation, code protection, or anti-tampering controls
• Lack of root or jailbreak detection
• Bypass of certificate pinning on rooted or jailbroken devices
• Lack of exploit mitigations in the binary (e.g., PIE, ARC, stack canaries)
• Path disclosure within the app binary
• Sensitive data in URLs or request bodies when transmitted over TLS
• OAuth secrets or app secrets hard-coded in the IPA/APK without demonstrated critical impact
• Sensitive information retained as plaintext in device memory without demonstrated extraction by an unprivileged attacker
• Crashes caused by malformed URL schemes, intents, or messages sent to exported activities/services/broadcast receivers without further impact
• Sensitive data stored in the app's private directory accessible only to the app itself
• Runtime hacking exploits (Frida, Appmon, etc.) requiring a jailbroken or rooted environment
• Shared content leaked through the system clipboard
• Reports based purely on static analysis of the binary without a runnable PoC demonstrating business logic impact
• Exposure of non-sensitive data on the device

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
• Accessing or modifying data belonging to other users
• Submitting AI-generated reports
• Spamming forms or account creation flows (even with low volume)