Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Lido

Bug bounty on Immunefi lido.fi

Accepting reports No KYC DAO Defi ETH
Go to program
Top reward
$2,000,000
Top severity paid
Critical
Assets in scope
29
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $2,000,000
for critical bugs, from $500.
Report on Immunefi
Submit through the program page.
Partial safe harbor
Some legal protection; read the terms.
Paid by USDC, USDS, DAI, USDT
No identity check to get paid.
No public write-ups
Keep findings private.

Rewards

What Immunefi lists as the payout for each severity.

Severity Reward
Critical Web $100,000 from $50,000
Critical Contract $2,000,000 10% of funds at risk · from $50,000
High Web $50,000 from $5,000
High Contract $250,000 from $10,000
Medium Web $5,000 from $1,000
Medium Contract $50,000 from $1,000
Low Web $500
Low Contract $1,000
Safe harbor
Partial Safe Harbor: for live, active exploits where immediate intervention is needed and normal disclosure is too slow.

Summarised with AI from the program policy on Immunefi, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

29 assets you may test.

Source code 19

  • https://github.com/lidofinance/aave-delivery-infrastructure
  • https://github.com/lidofinance/aragon-apps
  • https://github.com/lidofinance/circuit-breaker
  • https://github.com/lidofinance/community-staking-module
  • https://github.com/lidofinance/core
  • https://github.com/lidofinance/dual-governance
  • https://github.com/lidofinance/easy-track
  • https://github.com/lidofinance/governance-crosschain-bridges
  • https://github.com/lidofinance/lido-council-daemon
  • https://github.com/lidofinance/lido-keys-api
  • https://github.com/lidofinance/lido-l2
  • https://github.com/lidofinance/lido-l2-with-steth
  • https://github.com/lidofinance/lido-oracle
  • https://github.com/lidofinance/lido-vesting-escrow
  • https://github.com/lidofinance/mev-boost-relay-allowed-list
  • https://github.com/lidofinance/onchain-mon
  • https://github.com/lidofinance/oz-merkle-tree
  • https://github.com/lidofinance/stonks
  • https://github.com/lidofinance/validator-ejector

Domains 9

  • blog.lido.fi
  • csm.lido.fi
  • dao.lido.fi
  • docs.lido.fi
  • lido.fi
  • operators.lido.fi
  • stake.lido.fi
  • stvaults.lido.fi
  • trp.lido.fi

Smart contracts 1

  • https://docs.lido.fi/deployed-contracts

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Lido (via Immunefi)'s policy. "We" in these lines means the program, not this site.

While testing

  • All web and app bugs must come with a PoC in order to be accepted.
  • Proof of concept is always required for all severities.
  • Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
  • Public disclosure of an unpatched vulnerability in an embargoed bounty

Not accepted

  • Public disclosure of an unpatched vulnerability in an embargoed bounty
  • Automated testing of services that generates significant amounts of traffic
  • Any denial of service attacks that are executed against project assets
  • Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
  • Attempting phishing or other social engineering attacks against our contributors and/or stakers
  • Any testing with pricing oracles or third-party smart contracts
  • Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet

Summarised with AI from the program policy on Immunefi, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 56 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.

Search 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 Lido Lido is a liquid staking solution for Ethereum, backed by industry-leading staking providers and community stakers. It allows users to stake their ETH without locking up assets or maintaining infrastructure, while still participating in on-chain activities. ETH Defi DAO Liquid Staking Staking Solidity Vyper Maximum Bounty $2,000,000 Live Since 22 May 2021 Last Updated 29 June 2026 PoC Required Submit a Bug Information Scope Resources Rewards Lido provides rewards in USDC/USDS/DAI/USDT on Ethereum , denominated in USD. Rewards by Threat Level Smart Contract Critical Max: $2,000,000 Min: $50,000 Primacy of Rules High Max: $250,000 Min: $10,000 Primacy of Rules Medium Max: $50,000 Min: $1,000 Primacy of Rules Low Flat: $1,000 Primacy of Rules Critical Reward Calculation Mainnet assets: Reward amount is 10 % of the funds directly affected up to a maximum of: $2,000,000 Minimum reward to discourage security researchers from withholding a bug report: $50,000 Websites and Applications Critical Max: $100,000 Min: $50,000 Primacy of Rules High Max: $50,000 Min: $5,000 Primacy of Rules Medium Max: $5,000 Min: $1,000 Primacy of Rules Low Flat: $500 Primacy of Rules Rewards Body Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3 . This is a simplified 4-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit. All web and app bugs must come with a PoC in order to be accepted. All web and app bug reports without a PoC will be rejected with a request for a PoC. Smart Contracts Rewards Breakdown Critical Loss of user funds: When a minimum of 2,000,000 USD of assets is at risk Reward: Minimum 100,000 USD , Maximum 2,000,000 USD Loss of non-user funds (e.g., treasury): When a minimum of 1,000,000 USD of assets is at risk Reward: Minimum 50,000 USD , Maximum 1,000,000 USD High When a minimum of 250,000 USD of assets is at risk Reward: Minimum 10,000 USD , Maximum 250,000 USD Medium When a minimum of 50,000 USD of assets is at risk Reward: Minimum 1,000 USD , Maximum 50,000 USD Low Reward: 1,000 USD Web/App Rewards Breakdown Critical Reward: Minimum 50,000 USD , Maximum 100,000 USD High Reward: Minimum 5,000 USD , Maximum 50,000 USD Medium Reward: Minimum 1,000 USD , Maximum 5,000 USD Low Reward: 500 USD (Smart contracts Out Of Scope) Rewards on partner contracts are paid at contributors discretion. Reports regarding domains not listed under the scope section are paid at contributors discretion. Payouts are handled by the Lido contributors directly and are denominated in USD . Payouts can be done in USDC , USDS , DAI , or USDT , at the decision of the bug bounty hunter. View impacts in scope Program Overview Lido is a liquid staking solution for Ethereum, backed by industry-leading staking providers and community stakers. It allows users to stake their ETH without locking up assets or maintaining infrastructure, while still participating in on-chain activities. Lido aims to solve the key challenges of early Ethereum staking — illiquidity, immovability, and limited accessibility — by making staked ETH liquid and enabling participation with any amount. This helps strengthen the security of the Ethereum network. For more information about Lido, please visit Lido.fi . The bug bounty program covers its smart contracts and applications, focusing on preventing loss of user funds, some types of denial of service attacks, governance hijacks, data breaches, and data leaks. Relationship with Lido's Safe Harbor Program Bug Bounty is distinct from Lido's Safe Harbor Program : Bug bounty: for responsible disclosure of vulnerabilities before an active exploit, following Immunefi rules. Safe Harbor: for live, active exploits where immediate intervention is needed and normal disclosure is too slow. Safe Harbor and the Bug Bounty program are mutually exclusive from a rewards perspective. A Whitehat rewarded via the Bug Bounty program cannot receive a reward for the same exploit under Safe Harbor, even if Safe Harbor's legal protections apply. Known Issues Category Description / Link Last Updated At Smart Contract │ When someone creates a motion, its snapshot block is set to the current block.number. While, theoretically, it's totally correct and reasonable, there is a possibility to take a flashloan of the Lido governance token (LDO) and object the motion multiple times from different accounts until the objection threshold is reached. 30 May 2026 Category Smart Contract Description / Link When someone creates a motion, its snapshot block is set to the current block.number. While, theoretically, it's totally correct and reasonable, there is a possibility to take a flashloan of the Lido governance token (LDO) and object the motion multiple times from different accounts until the objection threshold is reached. Last Updated At 30 May 2026 KYC not required No KYC information is required for payout processing. Proof of Concept Proof of concept is always required for all severities. Prohibited Activities Program's custom prohibited activities Public disclosure of an unpatched vulnerability in an embargoed bounty Automated testing of services that generates significant amounts of traffic Any denial of service attacks that are executed against project assets Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks) Attempting phishing or other social engineering attacks against our contributors and/or stakers Any testing with pricing oracles or third-party smart contracts Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet Any other actions prohibited by the Immunefi Rules - https://immunefi.com/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 29