04 June 2021
Live since
KYC required
Maximum bounty

Program Overview

ApeSwap is a Decentralized Exchange / Automated Market Maker, Yield Farming, and Staking platform running on Binance Smart Chain, with lots of other features that let you earn and win tokens. ApeSwap was built by DeFi Apes, for DeFi Apes. They have a dedicated team of experienced monkeys, who have been in the crypto space for years. BANANA is the native currency of our platform. Stake, pool, and earn $BANANA (along with many other tokens) all on ApeSwap. For more information about ApeSwap, please visit https://apeswap.finance/.

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

The reward for critical smart contract vulnerabilities is further capped at 10% of economic damage, taking into account things like funds that are directly at risk.

Payouts are handled by the ApeSwap team directly and are denominated in USD. Payouts are done in BANANA or BUSD, at the discretion of the ApeSwap team.

Smart Contracts and Blockchain

up to USD $100,000
USD $30,000
USD $3,000
USD $1,500

Web and Apps

USD $7,500
USD $4,000
USD $1,500

Assets in Scope

Only web/app vulnerabilities that directly affect the web/app assets listed in this table and the subdomain highlighted are accepted within the bug bounty program. All others are out-of-scope.

Other smart contracts in production for ApeSwap not listed in this table may also be considered for the bug bounty program, especially if it affects user funds.

Additionally, the following GitHub repositories are shared for reference as they relate to the assets listed in the table. However, only vulnerabilities that affect the assets in production are considered as in-scope of the bug bounty program.

DEX https://github.com/ApeSwapFinance/apeswap-dex

MasterApe and Timelock https://github.com/ApeSwapFinance/apeswap-banana-farm

BANANA Token, Golden Banana, and Treasury https://github.com/ApeSwapFinance/apeswap-golden-banana

ApeRouter https://github.com/ApeSwapFinance/apeswap-swap-periphery

ApeFactory https://github.com/ApeSwapFinance/apeswap-swap-core

Prioritized Vulnerabilities

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Smart Contracts and Blockchain

  • Re-entrancy
  • Logic errors
    • including user authentication errors
  • Solidity/EVM details not considered
    • including integer over-/under-flow
    • Including rounding errors
    • including unhandled exceptions
  • Trusting trust/dependency vulnerabilities
    • including composability vulnerabilities
  • Oracle failure/manipulation
  • Novel governance attacks
  • Economic/financial attacks
    • including flash loan attacks
  • Congestion and scalability
    • including running out of gas
    • including block stuffing
    • including susceptibility to frontrunning
  • Consensus failures
  • Cryptography problems
    • Signature malleability
    • Susceptibility to replay attacks
    • Weak randomness
    • Weak encryption
  • Susceptibility to block timestamp manipulation
  • Missing access controls / unprotected internal or debugging interfaces

Websites and Apps

  • Remote Code Execution
  • Trusting trust/dependency vulnerabilities
  • Vertical Privilege Escalation
  • XML External Entities Injection
  • SQL Injection
  • Horizontal Privilege Escalation
  • Stored XSS
  • Reflective XSS with impact
  • CSRF with impact
  • Direct object reference
  • Internal SSRF
  • Session fixation
  • Insecure Deserialization
  • SSL misconfigurations
  • SSL/TLS issues (weak crypto, improper setup)
  • URL redirect
  • Clickjacking (must be accompanied with PoC)
  • Misleading Unicode text (e.g. using right to left override characters)

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