Triaged by Immunefi
PoC Required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Gain unauthorized access to critical internal services (e.g. databases, internal portals)
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)
Execute arbitrary system commands
Exploiting misconfigured IAM policies to gain unauthorized access to cloud infrastructure (e.g., virtual machines, storage buckets).
Disruption of critical backend services without overloading server with extensive traffic
Container escape leading to access to host system or other tenants
Network-level vulnerabilities allowing lateral movement, segmentation bypass, or unauthorized access to internal network segments
Unauthorized access to internal communication platforms (e.g., internal Slack, email, ticketing systems) leading to disclosure of confidential operational data
Disclosure of large-scale PII or sensitive information
Container security misconfigurations allowing privilege escalation within the container environment without full escape
Gain read-only access to internal infrastructure data (logs, configs, metrics)
Execute arbitrary system commands on non-core services
Out of scope
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
- 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
- Vulnerabilities affecting users of outdated browsers or platforms
- Most brute-forcing issues without a clear impact
- Vulnerabilities in third-party components (excluding critical vulnerabilities)
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
- 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
- Reports of open ports, exposed service banners, or fingerprinting of running services without demonstrated exploitation
- Subdomain takeover findings on abandoned or non-production subdomains without demonstrated impact on production systems or users
Prohibited Activities:
- 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
- Testing infrastructure vulnerabilities that may degrade, modify, or disrupt production systems is strictly prohibited. Researchers should demonstrate impact through read-only or proof-of-access actions whenever possible. Any active exploitation that modifies production state requires prior written approval from 1inch.