Deposit Manger / Withdrawal Address (swETH)

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/.](https://github.com/SwellNetwork/) However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Swell is a permissionless, non-custodial, and liquid (re)staking protocol designed for stakers, node operators, and the broader Ethereum ecosystem. 

Theft of users funds intended to be staked

Theft of funds in the Swell owned withdrawal addresses

Theft of funds in the Swell owned deposit contract

Theft of funds in transit from deposit contract to Beacon Chain contract

Manipulation of Swell’s ETH to swETH/rswETH conversion rate leading to the attacker obtaining a disproportionate amount of swETH/rswETH for staking ETH (> 10% difference compared to the last valid rate)

Attacker can cause the deposit of 32 ETH to the Beacon Chain to fail, losing funds

Execute arbitrary system commands

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)

Taking down the application/website

Taking down the NFT URI

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.

Changing the NFT metadata

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

Direct theft of user NFTs

Injection of malicious HTML or XSS through NFT metadata

Manipulation of wBTC to swBTC conversion rate leading to the attacker obtaining a disproportionate amount of swBTC for restaking swBTC (> 10% difference compared to the last valid rate)

Attacker can steal Node Operator or Swell Treasury fees

Attacker can force the exit of Swell validators

Attacker can change withdrawal address of Swell registered validators

Attacker can disable node operators

Injecting/modifying the static content on the target application without JavaScript (persistent), such as:  HTML injection without JavaScript, Replacing 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: 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

Attacker can pause Swell’s contracts

Attacker can modify Node Operator or Swell Treasury fee rate

Attacker can register themselves as a node operator

Attacker can obtain elevated access control privileges in Swell’s contracts

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 notifications

Injecting/modifying the static content on the target application without JavaScript (reflected), such as: Reflected HTML injection, Loading external site data

Redirecting users to malicious websites (open redirect)

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)

Taking over broken or expired outgoing links, such as: Social media handles, etc.

Temporarily disabling user to access target site, such as: Locking up the victim from login, Cookie bombing, etc.

Rewards are distributed according to the impact of the vulnerability based on the  [Immunefi Vulnerability Severity Classification System V2.2.](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-3/) 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 250 000__ for Critical smart contract bug reports.

Previously known issues highlighted in the following audit reports are considered as out of scope: 
- [https://github.com/SwellNetwork/v3-core-public/tree/master/Audit%20Reports](https://github.com/SwellNetwork/v3-core-public/tree/master/Audit%20Reports)

Payouts are handled by the __Swell__ team directly and are denominated in USD. However, payouts are done in __USDC__.