1inch - Infrastructure-logo

1inch - Infrastructure

|

The program focuses on identifying vulnerabilities that impact the infrastructure of 1inch. It complements our product-specific programs.

Maximum Bounty
$20,000
Live Since
11 June 2026
Last Updated
15 July 2026
  • Triaged by Immunefi

  • PoC Required

  • KYC required

Rewards

1inch - Infrastructure provides rewards in USDC on Ethereum, denominated in USD.

Rewards by Threat Level

Websites and Applications
Critical
Max: $20,000Min: $5,000
Primacy of Rules
High
Max: $5,000Min: $2,500
Primacy of Rules
Medium
Max: $2,500Min: $1,000
Primacy of Rules
Low
Max: $1,000Min: $100
Primacy of Rules

Primacy of Impact vs Primacy of Rules

1inch - Infrastructure adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.

Rewards Body

Rewards by Threat Level

Reward Calculation for Critical Level Reports

For critical infrastructure bugs, reports will be rewarded with the maximum critical reward (USD 20,000) only if the impact leads to:

  • Full compromise of production infrastructure (e.g., RCE on production servers, full IAM takeover)
  • Disclosure of credentials or secrets that grant attacker-level access to production systems and could lead to direct loss of user funds or critical data

All other impacts that would be classified as Critical would be rewarded a flat amount of 5000. The rest of the severity levels are paid out according to the Impact in Scope table.

Reward Calculation for High and Medium Level Reports

For High, Medium, and Low level reports, 1inch retains the full right to determine the reward amounts within the range provided due to the lack of objective scaling systems to determine the reward amount. It does not commit to rewarding anything above the base amounts. Rewards going above the base amounts are entirely within the discretion of the 1inch team.

Other Restrictions and Limitations

Vulnerabilities reported for blog.1inch.com, business.1inch.com (root subdomain), and assets falling under "Rest related to 1inch" are capped at Medium severity. The maximum reward for these assets is USD 2,500.

For the listed wildcard assets, only direct (one-level) subdomains of 1inch.com and 1inch.network are in scope. These cover any 1inch-controlled subdomain, asset, or service that is not explicitly listed in the Assets in Scope table but is verifiably operated by 1inch (e.g., reachable via DNS records under *.1inch.com or *.1inch.network and serving production traffic). Vulnerabilities in such assets are capped at Medium severity. 1inch reserves sole discretion to determine whether an asset qualifies.

Vulnerabilities affecting social media accounts (Telegram, Reddit, X/Twitter, Discord, and similar) are eligible only for impacts that result from a technical vulnerability directly attributable to 1inch's configuration or infrastructure, not from compromise of individual employee credentials, third-party platform vulnerabilities, or platform-wide issues affecting all users of that platform. Such reports are capped at High severity.

Reports combining multiple lower-severity findings into a meaningful impact will be evaluated based on the final combined demonstrated impact, not on individual components. Each component must still be a valid technical finding, and the chain must be reproducible end-to-end with a working PoC.

Gaps in logging, monitoring, or alerting are not eligible as standalone reports. They will only be considered as part of a report demonstrating exploitation of another in-scope vulnerability, where the absence of detection materially extends the attacker's window of opportunity. This must be demonstrated within the PoC, not asserted theoretically.

Additional Terms

For social media accounts, only impacts that affect those specific accounts/channels but do not affect all or others on those respective platforms on a platform-wide basis are considered as in-scope. All others are considered out-of-scope.

Any vulnerability discovered must be reported no later than 24 hours after the initial discovery. Reports submitted after this window may be considered at 1inch's discretion but are not guaranteed eligibility for a reward.

In cases where the same vulnerability is reported through multiple platforms, priority will be determined by the earlier submission timestamp, regardless of the platform used.

Reward Payment Terms

Payouts are handled by the 1inch 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.

Reports and payout details may be checked against OFAC, EU, and UK sanctions lists prior to payment. Payment may be withheld, delayed, or refused entirely if prohibited by applicable law, sanctions regimes, or 1inch's compliance obligations. Researchers are responsible for ensuring their participation does not violate the laws of their jurisdiction.

Program Overview

For more information about 1inch, please visit https://1inch.com/.

1inch provides rewards in USDC on Ethereum, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.

1inch maintains six additional bug bounty programs on Immunefi. In addition to this, they are:

KYC required

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

Participants must adhere to the Eligibility Criteria.

Proof of Concept

Proof of concept is always required for all severities.

Responsible Publication

Category 3: Approval Required

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.