![Swell-logo](/_next/image/?url=https%3A%2F%2Fimages.ctfassets.net%2Ft3wqy70tc3bv%2F49Iuyx7Sfkmzm6SI8INxX%2F91d54b122e661d32074e984b19f00741%2Fphoto_2023-04-18_14-31-24_copy.png&w=128&q=75)
Swell
Swell is a permissionless, non-custodial, and liquid ETH staking protocol that is built for stakers, node operators, and the Ethereum ecosystem.
ETH
Defi
Asset Management
Liquid Staking
Staking
Solidity
Maximum Bounty
$250,000Live Since
27 April 2023Last Updated
08 April 2024PoC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Critical
Theft of users funds intended to be staked
Critical
Theft of funds in the Swell owned withdrawal addresses
Critical
Theft of funds in the Swell owned deposit contract
Critical
Theft of funds in transit from deposit contract to Beacon Chain contract
Critical
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)
Critical
Attacker can cause the deposit of 32 ETH to the Beacon Chain to fail, losing funds
Critical
Execute arbitrary system commands
Critical
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)
Critical
Taking down the application/website
Critical
Taking down the NFT URI
Critical
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.
Critical
Changing the NFT metadata
Out of scope
Program's Out of Scope information
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 reflected HTML injection with or without javascript
- This does not exclude persistent plain text injection
- Self-XSS
- 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