SuperBots
SuperBots offers decentralized trading solutions, via "vaults" in which users can deposit their capital and which will be traded on decentralized markets in a secure manner. SuperBots offers a multitude of Vaults trading on DEX, and following precise trading strategies to get the most out of its capital.
PoC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Ability to execute system commands
Extract Sensitive data/files from the server such as /etc/passwd
Signing transactions for other users
Subdomain takeover resulting in financial loss (applicable for subdomains with addresses published)
Redirection of user deposits and withdrawals
Direct theft of user funds
Wallet interaction modification resulting in financial loss
Tampering with transactions submitted to the user’s wallet
Submitting malicious transactions to an already-connected wallet
Temporary freezing of funds for at least 1 day
Out of scope
- Best practice critiques
- Only public pages are concerned, namely under the extension app.superbots.finance. The admin dashboard and all other pages not intended for the public are out of scope.
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers
1.1k