PolyBunny

PolyBunny is a fork of PancakeBunny, one of the largest yield aggregators on BSC. By utilizing the same successful strategies as PancakeBunny, PolyBunny will be able to maximize returns while minimizing risk and continue building incentives for the PolyBUNNY token. The strategic importance of the Polygon fork is two-fold. First, conditions on Polygon substantially recapitulate the early conditions on BSC for which the tokenomics of PancakeBunny is optimized. We expect that, subject to the effective execution of the fork, we will be able to replicate on Polygon the virtuous cycle that PancakeBunny successfully created on BSC.

Second, over time, the Polygon fork will contribute significant cross-chain liquidity and fees to the PancakeBunny ecosystem, further amplifying important product innovations such as our Cross Chain Multiplexer suite.

For more information about PancakeBunny, please go to https://polygon.pancakebunny.finance/.

The bug bounty program covers its smart contracts and apps and is focused on receiving bug reports of the following impacts and attacks:

• Thefts and freezing of principal of any amount
• Thefts and freezing of unclaimed yield of any amount
• Theft of governance funds
• Governance activity disruption
• Website going down
• Flashloan attacks
• Oracle Manipulation attacks
• Reentrancy attacks

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. High and Critical smart contract bug reports are required to come with a proof of concept (PoC) for consideration of a reward.

Critical vulnerabilities for smart contract and blockchain vulnerabilities only get the classification if they have an impact of USD 100 000 or greater. If the impact is below that amount, the bug report is reclassified as High even if it would normally classify as Critical. Additionally, if a smart contract bug report with a classification of High has an impact of USD 100 000 or greater, it gets reclassified as Critical.

If a bug report is submitted to this bug bounty program and is validated and accepted, it cannot be resubmitted for the PancakeBunny bug bounty program.

Payouts are handled by the Pancake Bunny team directly and are denominated in USD. Payouts are done in USDT for rewards under USD 1 000 and are done in polyBUNNY for rewards that are greater. All rewards are paid over Polygon.

Only web/app vulnerabilities that directly affect the web/app assets listed in this table are accepted within the bug bounty program. All others, including anything only within https://pancakebunny.finance, are out-of-scope.

For added reference, please take a look at their GitHub - https://github.com/PancakeBunny-finance/PolygonBUNNY. However, only the contracts listed as in-scope here are considered as part 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 Contracts

• Thefts and freezing of principal of any amount
• Thefts and freezing of unclaimed yield of any amount
• Theft of governance funds
• Governance activity disruption

Website and Apps

• Redirected Funds by address modification
• Site goes down

We are especially interested in receiving and rewarding attacks of the following types, as long as they result in the impacts in scope:

Smart Contracts and Blockchain

• Oracle Manipulation
• Novel Governance Attacks
• Economic Exploit (including flash loans)
• Susceptibility to block timestamp manipulation
• Re-Entrancy

Websites and Apps

• Remote Code Execution
• Trusting trust/dependency vulnerabilities
• Vertical Privilege Escalation
• XML External Entities Injection
• SQL Injection
• LFI/RFI
• Horizontal Privilege Escalation
• Stored XSS
• Reflective XSS with impact
• CSRF with impact
• Direct object reference
• Internal SSRF
• Session fixation
• Insecure Deserialization
• DOM XSS
• 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)

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
• Logic errors
• Congestion and scalability

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