Swell is a permissionless, non-custodial, and liquid ETH staking protocol that is built for stakers, node operators, and the Ethereum ecosystem.
Swell provides users with an opportunity to earn yield on the ETH they hold through staking. This is done by staking ETH in conjunction with node operators that participate in validating the Ethereum proof-of-stake blockchain. The yield is earned through staking rewards received from the blockchain for validating block production.
Above all Swell aims to contribute to the Ethereum ecosystem and it’s users by simplifying the staking process as much as possible and driving utility for the reward-bearing token swETH.
For more information about Swell, please visit https://swellnetwork.io/.
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the 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 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.
Rewards for critical smart contract vulnerabilities are further capped at 10% of the funds at risk. In cases of repeatable attacks, only the first attack is considered unless the smart contract cannot be upgraded or paused. However, there is a minimum reward of USD 50 000 and a maximum reward of USD 100 000 for Critical smart contract bug reports.
Previously known issues highlighted in the following audit reports are considered as out of scope:
Payouts are handled by the Swell team directly and are denominated in USD. However, payouts are done in USDC.
- Up to USD $100,000
- USD $5,000
- USD $2,500
Websites and Applications
- USD $10,000
- USD $2,500
- USD $1,500
- USD $1,000
Assets in scope
- Smart Contract - swETHType
- Smart Contract - Deposit Manger / Withdrawal AddressType
- Smart Contract - Node Op RegistryType
- Smart Contract - Access Control ManagerType
- Websites and Applications - Web/AppType
Though only the proxy implementation contracts are listed as in-scope, current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy implementation smart contract as the target.
All smart contracts of Swell can be found at https://github.com/SwellNetwork/. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
Impacts in scope
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.
- Theft of users funds intended to be stakedCriticalImpact
- Theft of funds in the Swell owned withdrawal addressesCriticalImpact
- Theft of funds in the Swell owned deposit contractCriticalImpact
- Theft of funds in transit from deposit contract to Beacon Chain contractCriticalImpact
- Manipulation of Swell’s ETH to swETH conversion rate leading to the attacker obtaining a disproportionate amount of swETH for staking ETH (> 10% difference compared to the last valid rate)CriticalImpact
- Attacker can cause the deposit of 32 ETH to the Beacon Chain to fail, losing fundsCriticalImpact
- Attacker can steal Node Operator or Swell Treasury feesHighImpact
- Attacker can force the exit of Swell validatorsHighImpact
- Attacker can change withdrawal address of Swell registered validatorsHighImpact
- Attacker can disable node operatorsHighImpact
- Attacker can pause Swell’s contractsMediumImpact
- Attacker can modify Node Operator or Swell Treasury fee rateMediumImpact
- Attacker can register themselves as a node operatorMediumImpact
- Attacker can obtain elevated access control privileges in Swell’s contractsMediumImpact
Websites and Applications
- Execute arbitrary system commandsCriticalImpact
- Retrieve sensitive data/files from a running server, such as: /etc/shadow, database passwords, blockchain keys, (this does not include non-sensitive environment variables, open source code, or usernames)CriticalImpact
- Taking down the application/websiteCriticalImpact
- Taking down the NFT URICriticalImpact
- 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.CriticalImpact
- Changing the NFT metadataCriticalImpact
- Subdomain takeover with already-connected wallet interactionCriticalImpact
- Direct theft of user fundsCriticalImpact
- Malicious interactions with an already-connected wallet, such as: Modifying transaction arguments or parameters, Substituting contract addresses, Submitting malicious transactionsCriticalImpact
- Direct theft of user NFTsCriticalImpact
- Injection of malicious HTML or XSS through NFT metadataCriticalImpact
- 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.HighImpact
- Improperly disclosing confidential user information, such as: Email address, Phone number, Physical address, etc.HighImpact
- Subdomain takeover without already-connected wallet interactionHighImpact
- 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 name of user, Enabling/disabling notificationsMediumImpact
- Redirecting users to malicious websites (open redirect)MediumImpact
- 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 (demonstrate impact with PoC)LowImpact
- Taking over broken or expired outgoing links, such as: Social media handles, etc.LowImpact
- Temporarily disabling user to access target site, such as: Locking up the victim from login, Cookie bombing, etc.LowImpact
Out of Scope & Rules
The following vulnerabilities are excluded from the rewards for this bug bounty program:
- Attacks that the reporter has already exploited themselves, leading to damag
- Attacks requiring access to leaked keys/credentials
- Attacks requiring access to privileged addresses (governance, strategist)
Smart Contracts and Blockchain
- 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
Websites and Apps
- Theoretical vulnerabilities without any proof or demonstration
- Attacks requiring physical access to the victim device
- Attacks requiring access to the local network of the victim
- Reflected plain text injection ex: url parameters, path, etc.
- This does not exclude persistent plain text injection
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (ex: logout CSRF)
- Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
- Server-side non-confidential information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used only to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- DDoS vulnerabilities
- Feature requests
- Issues related to the frontend without concrete impact and PoC
- Best practices issues without concrete impact and PoC
- Vulnerabilities primarily caused by browser/plugin defects
- Leakage of non sensitive api keys ex: etherscan, Infura, Alchemy, etc.
- Any vulnerability exploit requiring browser bugs for exploitation. ex: CSP bypass
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