Stader for ETH
By Stader Bug bounty on Immunefi staderlabs.com
- Top reward
- $1,000,000
- Top severity paid
- Critical
- Assets in scope
- 21
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $1,000,000
- for critical bugs, from $20,000.
- Report on Immunefi
- Submit through the program page.
- Paid by USDC
- No identity check to get paid.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What Immunefi lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$1,000,000 10% of funds at risk · from $100,000 |
| High |
|
$100,000 |
| Medium |
|
$20,000 |
Scope
21 assets you may test.
Smart contracts 21
- https://etherscan.io/address/0x03ABEEC03BF39ac5A5C8886cF3496326d8164E1E
- https://etherscan.io/address/0x09134C643A6B95D342BdAf081Fa473338F066572
- https://etherscan.io/address/0x1DE458031bFbe5689deD5A8b9ed57e1E79EaB2A4
- https://etherscan.io/address/0x3073cC90aD39E0C30bb0d4c70F981FbD00f3458f
- https://etherscan.io/address/0x4ABEF2263d5A5ED582FC9A9789a41D85b68d69DB
- https://etherscan.io/address/0x4f4Bfa0861F62309934a5551E0B2541Ee82fdcF1
- https://etherscan.io/address/0x62e0b431990Ea128fe685E764FB04e7d604603B0
- https://etherscan.io/address/0x7Af4730cc8EbAd1a050dcad5c03c33D2793EE91f
- https://etherscan.io/address/0x84645f1B80475992Df2C65c28bE6688d15dc6ED6
- https://etherscan.io/address/0x84ffDC9De310144D889540A49052F6d1AdB2C335
- https://etherscan.io/address/0x85A22763f94D703d2ee39E9374616ae4C1612569
- https://etherscan.io/address/0x97c92752DD8a8947cE453d3e35D2cad5857367af
- https://etherscan.io/address/0x9d4C3166c59412CEdBe7d901f5fDe41903a1d6Fc
- https://etherscan.io/address/0x9F0491B32DBce587c50c4C43AB303b06478193A7
- https://etherscan.io/address/0xA35b1B31Ce002FBF2058D22F30f95D405200A15b
- https://etherscan.io/address/0xaf42d795A6D279e9DCc19DC0eE1cE3ecd4ecf5dD
- https://etherscan.io/address/0xbe3781CE437Cc3fC8c8167913B4d462347D11F20
- https://etherscan.io/address/0xcf5EA1b38380f6aF39068375516Daf40Ed70D299
- https://etherscan.io/address/0xd1a72Bd052e0d65B7c26D3dd97A98B74AcbBb6c5
- https://etherscan.io/address/0xeDA89ed8F89D786D816F8E14CF8d2F90c6BF763f
- https://etherscan.io/address/0xF64bAe65f6f2a5277571143A24FaaFDFC0C2a737
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Stader for ETH (via Immunefi)'s policy. "We" in these lines means the program, not this site.
While testing
-
Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
-
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 that are executed against project assets
-
Automated testing of services that generates significant amounts of traffic
-
Public disclosure of an unpatched vulnerability in an embargoed bounty
-
Any other actions prohibited by the Immunefi Rules
Not accepted
-
SD Auction final bid price can be gamed by MEV optimization. (This is intended)
-
Node Operator can avoid small portion of validator penalty by exiting at the right time.
-
ER update via chainlink may return incorrect or state data as it is not implemented yet
-
Protocol will not benefit from slashing mechanism when remaining penalty bigger than minThreshold of SD
-
Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
Summarised with AI from the program policy on Immunefi, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 57 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from immunefi.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Back to Explore Stader for ETH Stader is a non-custodial smart contract based staking platform that helps you conveniently discover and access staking solutions. ETH Defi Staking Solidity Maximum Bounty $1,000,000 Live Since 08 July 2023 Last Updated 01 January 2025 PoC Required Submit a Bug Information Scope Resources Rewards Stader for ETH provides rewards in USDC on Ethereum , denominated in USD. Rewards by Threat Level Smart Contract Critical Max: $1,000,000 Min: $100,000 Primacy of Impact High Flat: $100,000 Primacy of Impact Medium Flat: $20,000 Primacy of Impact Critical Reward Calculation Mainnet assets: Reward amount is 10 % of the funds directly affected up to a maximum of: $1,000,000 Minimum reward to discourage security researchers from withholding a bug report: $100,000 Rewards Body Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. Reward Calculation for Critical Level Reports For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 1 000 000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 100 000 is to be rewarded in order to incentivize security researchers against withholding a bug report. Repeatable Attack Limitations In cases of repeatable attacks for smart contract bugs, only the first attack will be counted, regardless of whether the smart contract is upgradable, pausable, or killable. Public Disclosure of Known Issues Bug reports covering previously-discovered bugs acknowledged below are not eligible for any reward through the bug bounty program. SD Auction final bid price can be gamed by MEV optimization. (This is intended) Node Operator can avoid small portion of validator penalty by exiting at the right time. (This is limited to once per validator and cost of exiting and reactivation does not justify penalty saved) ER update via chainlink may return incorrect or state data as it is not implemented yet, Currently ER data is submitted by oracle members. Protocol will not benefit from slashing mechanism when remaining penalty bigger than minThreshold of SD Previous Audits Stader has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward. https://www.staderlabs.com/audits/ethereum/smartcontracts/ETHx_SmartContract_Audit_Report_by_Halborn_v2.pdf https://www.staderlabs.com/audits/ethereum/smartcontracts/ETHx_SmartContract_audit_report_by_SigmaPrime_v2.pdf Proof of Concept (PoC) Requirements A PoC is required for the following severity levels: Smart Contract - Critical Smart Contract - High Smart Contract - Medium All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules . Bug report submissions without a PoC when a PoC is required will not be provided with a reward. Reward Payment Terms Payouts are handled by the Stader team directly and are denominated in USD. However, payments are done in USDC. View impacts in scope Program Overview Stader is a non-custodial smart contract based staking platform that helps you conveniently discover and access staking solutions. Stader has built liquid staking tokens on Polygon, BNB, Fantom, among others. For more information about Stader for ETH, please visit https://www.staderlabs.com/eth/ Stader provides rewards in USDC. For more details about the payment process, please view the Rewards by Threat Level section further below. Primacy of Impact vs Primacy of Rules Stader adheres to the Primacy of Impact for the following severity levels: Smart Contract - Critical Smart Contract - High If a category’s severity level is covered within the Primacy of Impact, it means that even if the impacted asset is not in-scope but is owned by the project, then it would be considered as in-scope of the bug bounty program as long as it involves an impact under that respective severity level. When submitting a report, just select the Primacy of Impact asset placeholder. If the team behind this project has multiple projects, those other projects are not covered under the Primacy of Impact of this program. Instead, check if those other projects have a bug bounty program on Immunefi. Testnet and mock files are not covered under the Primacy of Impact. All other severity levels not listed here are considered under the Primacy of Rules, which means that they are bound by the terms of the bug bounty program. Immunefi Standard Badge Stader has satisfied the requirements for the Immunefi Standard Badge , which is given to projects that adhere to our best practices. KYC not required No KYC information is required for payout processing. Proof of Concept Proof of concept is always required for all severities. Responsible Publication Category 3: Approval Required Prohibited Activities Default prohibited activities Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet 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 that are executed against project assets Automated testing of services that generates significant amounts of traffic Public disclosure of an unpatched vulnerability in an embargoed bounty Any other actions prohibited by the Immunefi Rules Feasibility Limitations The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report. Chain Rollbacks Pre-Impact Bug Monitoring Attack Investment Amount Attacks With A Financial Risk To The Attacker When Is An Impactful Attack Downgraded To Griefing? Submit a Bug Total Assets in Scope 22