🐞
Bug Bounty
Join our bug bounty program with Immunefi!
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.1. 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 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:
Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage. The primary consideration is the funds affected, in addition to PR and brand considerations, at the team's discretion. However, there is a minimum reward of USD 100 000 for Critical smart contract bug reports.
Critical website and application bug reports will be rewarded with USD 100 000 only if the impact leads to a direct loss in funds. All other effects classified as Critical would be rewarded no more than USD 20 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 team's discretion.
To prevent any attack on Wombat, kindly allow us ample time to fix the problem before publishing your findings publicly. Doing so may lead to your rewards being rescinded.
Target | Type |
|---|---|
Smart Contract - Pool | |
Smart Contract - LP-BUSD | |
Smart Contract - LP-USDC | |
Smart Contract - LP-USDT | |
Smart Contract - LP-DAI | |
Web/App | |
Web/App |
All smart contracts of Wombat Exchange can be found at https://github.com/wombat-exchange/v1-core. However, only those in the Assets in Scope table are considered 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 effect is in the Impacts in Scope section below, you are encouraged to submit it for consideration by the project.
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in scope, even if they affect something in the assets in the scope table.
- Any governance voting result manipulation
- Direct theft of any user funds, whether at rest or in motion, other than unclaimed yield
- Permanent freezing of funds
- Miner-extractable value (MEV)
- Protocol Insolvency
- Theft of unclaimed yield
- Permanent freezing of unclaimed yield
- Temporary freezing of funds for at least 24 hours
- Smart contracts are unable to operate due to a 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)
- Theft of gas
- Unbounded gas consumption
- Smart contract fails to deliver promised returns but doesn’t lose 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)
- 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. Subdomain takeover with already-connected wallet interaction
- Direct theft of user funds
- Malicious interactions with an already-connected wallet, such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions
- Injecting/modifying the static content on the target application without Javascript (Persistent), such as HTML injection without Javascript, replacing the 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 the email or password of the victim, etc.
- Improperly disclosing confidential user information such as email address, phone number, physical address, etc.
- Subdomain takeover without already-connected wallet interaction
- 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 a user or enabling/disabling notifications
- 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)
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)
- 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
- Centralization risks
- 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 are 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
- Vulnerabilities are primarily caused by browser/plugin defects.
- Any vulnerability exploit requiring CSP bypass resulting from a browser bug
The following activities are prohibited by this 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
Last modified 10mo ago