All smart contracts of Wombat Exchange can be found at [https://github.com/wombat-exchange/v1-core](https://github.com/wombat-exchange/v1-core). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If a Critical or High severity impact can be caused to any other asset managed by Wombat Exchange that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.

The Wombat Team has created an algorithm that redefines the stable swap experience, bringing greater capital efficiency to fuel DeFi growth and adoption.

Any governance voting result manipulation

Permanent freezing of funds

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Miner-extractable value (MEV)

Protocol Insolvency

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)

Taking down the application/website

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.

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

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Temporary freezing of funds for at least 24 hours

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.

Subdomain takeover without already-connected wallet interaction

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

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

Theft of gas

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)

Smart contract fails to deliver promised returns, but doesn’t lose value

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2). This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All web/app and all Critical severity smart contract bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

All issues previously highlighted in the following audit reports are considered out of scope: 
  - [https://docs.wombat.exchange/resources/security-audits](https://docs.wombat.exchange/resources/security-audits)

Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. 

Critical website and application bug reports will be rewarded with __USD 10 000__ only if the impact leads to a direct loss in funds. All other impacts that would be classified as Critical would be rewarded no more than __USD 2 000__.

Payouts are handled by the __Wombat Exchange__ team directly and are denominated in USD. However, payouts are done in __USDC__ or __USDT__, at the discretion of the team.

Wombat Exchange

Resources & Documentation