Superform
The Superform Protocol is a suite of non-upgradeable, non-custodial smart contracts that act as a central repository for yield and a router for users.
Arbitrum
Avalanche
BSC
Base
ETH
Optimism
Polygon
Defi
Crosschain Liquidity
Yield Aggregator
Solidity
Maximum Bounty
$200,000Live Since
25 January 2024Last Updated
09 July 2025PoC Required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Severity
Critical
Title
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Severity
Critical
Title
Direct theft of SuperPositions
Severity
Critical
Title
Permanent freezing of funds
Severity
Critical
Title
Permanent freezing of SuperPositions
Severity
Critical
Title
Unauthorized minting of SuperPositions
Severity
Critical
Title
Protocol insolvency
Severity
High
Title
Theft of unclaimed yield
Severity
High
Title
Theft of unclaimed rewards
Severity
High
Title
Permanent freezing of unclaimed yield
Severity
High
Title
Permanent freezing of unclaimed rewards
Severity
High
Title
Temporary freezing of funds
Severity
High
Title
Temporary freezing of SuperPositions
Out of scope
Program's Out of Scope information
These impacts are out of scope for this bug bounty program.
- Impacts related to gas griefing vulnerabilities in AMB Implementations
- Impacts related to stale prices on helper contracts which are used for off-chain purposes
- Impacts related to gas griefing vulnerabilities in AMB Implementations
- Impacts related to stale prices on helper contracts which are used for off-chain purposes
Default Out of Scope and rules
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