1inch - Wallet-logo

1inch - Wallet

The 1inch Wallet is a multichain non-custodial DeFi crypto wallet with an easy interface for secure storage and transactions.

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

  • PoC Required

  • KYC required

Rewards

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

Rewards by Threat Level

Websites and Applications
Critical
Max: $100,000Min: $30,000
Primacy of Rules
High
Max: $30,000Min: $10,000
Primacy of Rules
Medium
Max: $10,000Min: $2,000
Primacy of Rules
Low
Max: $2,000Min: $100
Primacy of Rules

Primacy of Impact vs Primacy of Rules

1inch - Wallet 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

Rewards are distributed according to the impact of the vulnerability based on the Impacts in Scope table.

Reward Calculation for Critical Level Reports

For critical web/apps bugs, reports will be rewarded with 100000, only if the impact leads to:

  • A loss of funds involving an attack that does not require any user action
  • Private key or private key generation leakage leading to unauthorized access to user funds

All other impacts for assets with those designations that would be classified as Critical would be rewarded a flat amount of 30000.

Reward Calculation for Other Levels

High, Medium, and Low reports are rewarded at a flat rate of USD 10 000, USD 2 000, and USD 100, respectively. At the discretion of 1inch, it may decide to increase the reward paid out to security researchers for exceptional cases. However, it makes no commitment to rewarding above these amounts. The maximum reward listed on the table provided is only as guidance for the maximum that could ever be expected in even the most exceptional cases within those severity levels.

Other Restrictions and Limitations

The listed app store URLs reference the official 1inch Wallet applications. Testing should be performed against the latest production version of the wallet downloaded from the listed app stores. Beta, staging, or modified builds (including but not limited to APKs from third-party sources, side-loaded variants, or self-built versions) are not considered as production assets and fall under the non-production severity cap above.

Additional Terms

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.