Please note that for Website/App, only [https://pancakeswap.finance](https://pancakeswap.finance) is in scope. Other subdomains are not in scope.

OFT related contracts are not in the scope of this program, unless the logic is specific to PancakeSwap’s implementation.

If you have found an issue with OFT related contracts, please report it to [https://immunefi.com/bounty/layerzero/](https://immunefi.com/bounty/layerzero/). 

PancakeSwap is a decentralized exchange running on Binance Smart Chain and other multiple chains, with lots of other features that let you earn and win tokens. It's fast, cheap, and anyone can use it. It's also got pancakes and rabbits.

Any governance voting result manipulation

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield (dependent on the value at stake)

Permanent freezing of funds (dependent on the value at stake)

Protocol Insolvency (dependent of the shortfall in value)

Execute arbitrary system commands

Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)

Direct theft of user funds

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc.

Subdomain takeover with already-connected wallet interaction

Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions

Complete theft of unclaimed yield (dependent on the value at stake)

Temporary freezing of funds (dependent on the value at stake and duration of freeze)

Permanent freezing of unclaimed yield (dependent on the value at stake and duration of freeze)

Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.

Improperly disclosing confidential user information such as email address, phone number, physical address, etc.

Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as changing the first/last name of user, or en/disabling notification

Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site data

Redirecting users to malicious websites (Open Redirect)

Subdomain takeover without already-connected wallet interaction

Smart contract unable to operate due to lack of token funds

Block stuffing for profit

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Unbounded gas consumption that results in denial of service

Theft of gas

Changing details of other users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction such as iframing leading to modifying the backend/browser state (PoC required)

Taking over broken or expired outgoing links such as social media handles, etc.

Temporarily disabling user to access target site, such as locking up the victim from login, cookie bombing, etc.

Rewards are distributed according to the impact of the vulnerability based on
the [Immunefi Vulnerability Severity Classification System 2.2](https://immunefi.com/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.

Smart Contract rewards are classified by __Group 1__ and __Group 2__. 

__Group 1__ consists of the core swap and reward components such as:

AMM: Pancakeswap V2, V3, Stableswap and related periphery contracts
Staking: Masterchef V2, V3, Smart Chef (Syrup pools), Cake Pool

__Group 2__ consists of other contracts not mentioned in group 1.

Group 1 rewards are notated in the rewards table by the higher ranges listed by severity level, while Group 2 rewards are notated by the lower ranges listed by severity level.

All bug reports must include a Proof of Concept demonstrating how the vulnerability can be exploited to be eligible for a reward. 

The final reward amount for critical vulnerabilities is capped at 10% of the funds at risk based on the vulnerability reported.

Critical smart contract vulnerability payouts for Group 1 are a minimum of __USD $50,000__, or 10% of the value at risk at the time of report submission, with a hard cap of __USD $1,000,000__, whichever is larger. Value at risk should be calculated primarily (though not exclusively) based on concrete and demonstrable funds at risk. Any supplementary reward beyond the minimum __USD $50,000__ or 10% of value at risk is at the discretion of the team.

Critical smart contract vulnerability payouts for Group 2 are a minimum of __USD $20,000__, or 10% of the value at risk at the time of report submission, with a hard cap of __USD $100,000__, whichever is larger. Value at risk should be calculated primarily (though not exclusively) based on concrete and demonstrable funds at risk. Any supplementary reward beyond the minimum __USD $20,000__ or 10% of value at risk is at the discretion of the team.

All non-critical rewards for the project bug bounty program are scaled based on an internally established team criteria, taking into account the exploitability of the bug, the impact it causes, and the likelihood of the vulnerability presenting itself, which is especially factored in with bug reports requiring multiple conditions to be met that are currently not in-place. Rewards will be provided at the determined fair value by the team depending on these conditions, assuming that the bug report is in-scope of the bug bounty program.

XSS reports are restricted to those that have an impact of prompting a user to  sign a transaction or a redirect.

All payouts are done by the **PancakeSwap** team and are pegged to the **USD** values set here and are payable in **CAKE** or **USDT**.

PancakeSwap

Resources & Documentation