07 June 2021
Live since
No
KYC required
$25,000
Maximum bounty
20 October 2022
Last updated

Program Overview

Zapper is your DeFi dashboard for monitoring your portfolio, including assets, debts, liquidity pools, staking, claimable rewards, and yield farming activities–but it requires you to share no personal data! Just connect your Ethereum wallet or paste in the ETH wallet address / ENS domain.

Zapper is also your gateway to investing in hundreds of DeFi strategies in just a few clicks. Zaps save time, effort, and often transaction fees (gas) by deploying capital in a single DeFi command control center, working with the most trusted DeFi applications like yearn.finance, Uniswap, Balancer, Curve, and more.

For a full overview of Zapper, please visit https://zapper.fi/.

The bug bounty program covers its smart contracts and apps and is focused on the prevention of loss of user funds.

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.

All web and app bugs must come with a PoC in order to be accepted. All web and app bug reports without a PoC will be rejected with a request for a PoC.

Payouts are handled by the Zapper team directly and are denominated in USD. Payouts are done in USDC or DAI. Bug bounty hunters however must specify where they want to receive the tokens on, whether on Ethereum, Polygon, or Binance Smart Chain.

Smart Contract

Critical
Level
USD $25,000
Payout
High
Level
USD $10,000
Payout
Medium
Level
USD $1,000
Payout
Low
Level
USD $250
Payout

Websites and Applications

High
Level
USD $7,500
Payout
PoC Required
Medium
Level
USD $1,000
Payout
PoC Required
Low
Level
USD $250
Payout
PoC Required

Assets in scope

For additional reference, you can visit the Zapper GitHub repositories. However, only the assets listed in this table are considered as in-scope of the bug bounty program.

For web vulnerabilities, only https://zapper.fi is in scope. Any subdomains are considered out-of-scope.

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

  • Critical Smart Contract Impact
    Critical
    Impact
  • High Smart Contract Impact
    High
    Impact
  • Medium Smart Contract Impact
    Medium
    Impact
  • Low Smart Contract Impact
    Low
    Impact

Websites and Applications

  • High Websites and Applications Impact
    High
    Impact
  • Medium Websites and Applications Impact
    Medium
    Impact
  • Low Websites and Applications Impact
    Low
    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 and Blockchain

  • 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

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 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