Instadapp

Submit a Bug
20 September 2021
Live since
No
KYC required
$500,000
Maximum bounty
28 May 2024
Last updated

Program Overview

The Instadapp platform offers a comprehensive suite of tools for both users and developers to harness the full potential of DeFi. With products ranging from refinancing and flashloan strategies to lending platforms and smart wallet protocols, Instadapp aims to optimize DeFi interactions.

This bug bounty program covers the following protocols and services:

Instadapp PRO (DeFi Smart Accounts)

Instadapp PRO is a comprehensive platform for managing and utilizing DeFI, users can access the top lending protocols and maximize their gains by leveraging and refinancing between protocols. Instadapp Pro allows users to execute advanced swaps and other complex transactions.

Avocado Smart Wallet

Avocado is a next generation Account Abstraction wallet created by the Instadapp Team. Avocado abstracts networks, gas and addresses making it easier to interact with the growing and complex web3 world. Avocado features a unified USDC gas tank, mass payments, cross chain transaction, transaction previews, built in DEX and Bridging services and 2FA security.

Fluid

Fluid works as a multi-layered protocol with a unified liquidity layer that enables many protocols to be built on top:

  • Fluid Liquidity Layer: The base liquidity protocol for Fluid, all liquidity and protocols draw their liquidity from the liquidity layer.
  • Fluid Lending Protocol: foundational component designed to facilitate secure and highly efficient lending. You can think of it as the 'Deposit and Earn' of Fluid.
  • Fluid Vault Protocol: The first protocol built on top of the Liquidity Layer, the vault protocol enables users to supply assets and borrow against them in a single-asset/single-debt vault similar to MakerDAO.

For more information about Instadapp, please visit https://instadapp.io/.

This bug bounty program is focused on their smart contracts and dapp and is focused on preventing the following impacts:

  • Deletion of user data
  • Theft of governance funds
  • Thefts and freezing of principal of any amount
  • Thefts and freezing of unclaimed yield of any amount

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.

Reward Calculation for Critical Level Reports

For critical smart contract vulnerabilities, the reward is 10% of the directly affected funds, up to a maximum of USD 500,000. The calculation considers the funds at risk based on the bug report submission date and time. There is a minimum guaranteed reward of USD 25,000 to encourage reporting even for smaller valued critical bugs.

Reward Calculation for High Level Reports

For high smart contract impacts, the reward is capped at $100,000 and is based on 50% of the value of the affected funds. The calculation considers the funds at risk based on the bug report submission date and time. There is a minimum guaranteed reward of USD 5,000 to encourage reporting even for smaller valued critical bugs.

Secondary/Market Attack on Fluid

Fluid as a lending protocol utilizes different aspects of the blockchain which may indirectly affect the protocol. The following outline conditions for particular secondary attacks that are not directly on the Fluid contracts, but that have secondary or associated effects to the Fluid contracts may be considered for a reward:

  • The attack must directly impact Fluid i.e an attack which affects the broader market such as price manipulation but is not targeting Fluid would not qualify.

Examples of secondary attacks would be:

  • Manipulation of a DEX or on Chain price oracle from a secondary source, which results in the immediate and total loss of funds of the Fluid protocol, where the attack is specifically targeting Fluid protocol.
  • Flash Loan based attack that would cause immediate and irreversible financial loss to Fluid protocol; where the attack is specifically targeting the Fluid protocol, this would exclude attacks which manipulate the price of a single token used on Fluid.

Prior published audits are here for review, any noted vulnerability or bugs in previously completed audits are not eligible for a reward.

Defi Smart Accounts (DSA)/Instadapp PRO

Avocado

Fluid

Proof of Concept (PoC) Requirements

A PoC is required for the following severity levels:

  • Smart Contract - Critical
  • Smart Contract - High

When calculating the USD value of total value locked (TVL) to determine funds at risk, outstanding borrows are excluded.

To be eligible for a reward, the vulnerability must exist in the deployed smart contract.

Bugs resulting in temporary freezing of funds are not eligible for a reward.

Payouts are handled by the Instadapp team directly and are denominated in USD. However, payouts are done in stablecoins like, USDC, USDT and DAI at the discretion of the team.

Smart Contract

Critical
Level
USD $25,000 - USD $500,000
Payout
PoC Required
High
Level
USD $5,000 - USD $100,000
Payout
PoC Required

Websites and Applications

Critical
Level
USD $5,000 - USD $50,000
Payout
PoC Required
High
Level
USD $5,000 - $10,000
Payout
PoC Required

Assets in scope

All code of Instadapp can be found at https://github.com/Instadapp. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

All folders and files labeled with the words “test”, “mock/mocks”, or “dummy” are out-of-scope of the bug bounty program.

Impacts in scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Smart Contract

  • Any governance voting result manipulation
    Critical
    Impact
  • Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield (Connectors are out of scope from this)
    Critical
    Impact
  • Permanent freezing of funds
    Critical
    Impact
  • Protocol Insolvency
    Critical
    Impact
  • Theft of unclaimed yield
    High
    Impact
  • Miner-extractable value (MEV)
    High
    Impact
  • Permanent freezing of unclaimed yield
    High
    Impact
  • Temporary freezing of funds (more than 10 Days)
    High
    Impact

Websites and Applications

  • Ability to execute system commands
    Critical
    Impact
  • Extract Sensitive data/files from the server such as /etc/password
    Critical
    Impact
  • Bypassing Authentication
    Critical
    Impact
  • Signing transactions for other users
    Critical
    Impact
  • Redirection of user deposits and withdrawals
    Critical
    Impact
  • Subdomain takeover resulting in financial loss (applicable for subdomains with addresses published)
    Critical
    Impact
  • Wallet interaction modification resulting in financial loss
    Critical
    Impact
  • Direct theft of user funds
    Critical
    Impact
  • Tampering with transactions submitted to the user’s wallet
    Critical
    Impact
  • Submitting malicious transactions to an already-connected wallet
    Critical
    Impact
  • Spoofing content on the target application (Persistent)
    High
    Impact
  • Users Confidential information disclosure such as Email
    High
    Impact
  • Privilege escalation to access unauthorized functionalities
    High
    Impact
  • Third-Party API keys leakage that demonstrates loss of funds or modification on the website
    High
    Impact
  • Redirecting users to malicious websites (Open Redirect)
    High
    Impact

Out of Scope & Rules

The following vulnerabilities are excluded from the rewards for this bug bounty program:

  • Attacks that the reporter has already exploited themselves, leading to damage
  • Attacks requiring access to leaked keys/credentials
  • Attacks requiring access to privileged addresses (governance, strategist)

Smart Contracts

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Basic economic governance attacks (e.g. 51% attack)
  • Lack of liquidity
  • Best practice critiques
  • Sybil attacks
  • Griefing involving gas fees alone

Websites and Apps

  • Theoretical vulnerabilities without any proof or demonstration
  • Content spoofing / Text injection issues
  • Self-XSS
  • Captcha bypass using OCR
  • CSRF with no security impact (logout CSRF, change language, etc.)
  • Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
  • Server-side information disclosure such as IPs, server names, and most stack traces
  • Vulnerabilities used to enumerate or confirm the existence of users or tenants
  • Vulnerabilities requiring unlikely user actions
  • URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
  • Lack of SSL/TLS best practices
  • DDoS vulnerabilities
  • Attacks requiring privileged access from within the organization
  • Feature requests
  • Best practices

The following activities are prohibited by this bug bounty program:

  • Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
  • 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
  • Automated testing of services that generates significant amounts of traffic
  • Public disclosure of an unpatched vulnerability in an embargoed bounty