EigenLayer is a protocol built on Ethereum that introduces restaking, a new primitive in cryptoeconomic security. This primitive enables the reuse of ETH on the consensus layer. Users that stake ETH natively or with a liquid staking token (LST) can opt-in to EigenLayer smart contracts to restake their ETH or LST and extend cryptoeconomic security to additional applications on the network to earn additional rewards.
For more information about EigenLayer, please visit https://www.eigenlayer.xyz/.
EigenLayer provides rewards in USDC. For more details about the payment process, please view the Rewards by Threat Level section further below.
EigenLayer adheres to category 3. This Policy determines what information whitehats are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.
Primacy of Impact vs Primacy of Rules
EigenLayer adheres to the Primacy of Impact for the following severity levels:
- Smart Contract, Critical Severity Level
- Smart Contract, High Severity Level
- Smart Contract, Medium Severity Level
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. Additionally, if the impact is primarily limited to code that is currently paused, EigenLayer reserves the right to downgrade or reject the report.
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.
Known Issue Assurance
EigenLayer commits to providing Known Issue Assurance to bug submissions through their program. This means that EigenLayer will either disclose known issues publicly or at the very least privately via a self-reported bug submission in order to allow for a more objective and streamlined mediation process to prove that an issue is known. Otherwise, assuming the bug report itself is valid, it would result in the bug report being considered in-scope and due 100% of the reward with respect to the bug bounty program terms.
Immunefi Standard Badge
EigenLayer has satisfied the requirements for the Immunefi Standard Badge, which is given to projects that adhere to our best practices.
Rewards by Threat Level
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 2,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 250,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.
For Critical website and application bug reports, the reward amount is 10% of the funds directly affected up to a maximum of USD 100,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 50,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.
Reward Calculation for High Level Reports
For High Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 250,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 50,000 is to be rewarded in order to incentivize security researchers against withholding a bug report.
EigenLayer has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
- Any audits listed at https://docs.eigenlayer.xyz/overview/audits
Bug reports that require an attack that involve one or more other protocols (e.g. utilizing flash loans from a margin protocol or manipulating the spot prices on a DEX), either to make an attack more severe than it would be in isolation, or to achieve an attack that would otherwise be impossible or infeasible, would be out of scope. However, they will be considered as in-scope and categorized according to the program rules as long as all of the following are true:
- Losses or other negative effects of the attack are inflicted upon EigenLayer ecosystem participants
- The additional protocols used must have enough liquidity in various assets to allow the attack to succeed at the time of bug report submission. For example: if an attack requires an ETH flash loan, but the amount is larger than all the ETH available for loan across the ecosystem
If issues are associated with the pausing functionality of the contract, then the severity will depend on whether the feature was paused or not at the time of the report.
Proof of Concept (PoC) Requirements
A PoC is required for the following severity levels:
- Smart Contracts, Critical Severity Level
- Smart Contracts, High Severity Level
- Smart Contracts, Medium Severity Level
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 EigenLayer team directly and are denominated in USD. However, payments are done in USDC.
- USD $250,000 to USD $2,000,000
- USD $50,000 to USD $250,000
- USD $10,000 to USD $30,000
Websites and Applications
- USD $50,000 to USD $100,000
- USD $10,000 to $25,000
- USD $2,000 to USD $5,000
Assets in scope
- Smart Contract - DelegationManager.sol - Transparent Upgradeable Proxy - the current implementation is considered in-scopeType
- Smart Contract - StrategyManager.sol - Transparent Upgradeable Proxy - the current implementation is considered in-scopeType
- Smart Contract - StrategyBase.sol - Transparent Upgradeable Proxy - the current implementation is considered in-scopeType
- Smart Contract - DelayedWithdrawalRouter.sol - Transparent Upgradeable Proxy - the current implementation is considered in-scopeType
- Smart Contract - EigenPod.sol - Upgradeable Beacon Proxy - the current implementation is considered in-scopeType
- Smart Contract - EigenPodManager.sol - Transparent Upgradeable Proxy - the current implementation is considered in-scopeType
- Smart Contract - PauserRegistry.solType
- TargetSmart Contract - Primacy of ImpactType
- Websites and Applications - DelayedWithdrawalRouter.solType
All code of EigenLayer can be found at https://github.com/Layr-Labs/eigenlayer-contracts. Check “releases” to view code from the most recent mainnet deployment.
Most of EigenLayer’s smart contracts are pausable. For any pausable contract, functions which are currently paused are considered out-of-scope, unless an exploit includes a means to bypass pausability.
Most of EigenLayer’s smart contracts are upgradeable. For any upgradeable contract, the current implementation on ETH mainnet is considered in-scope, while no-longer-used implementations are considered out-of-scope. Deployed contract addresses on ETH mainnet should be documented in https://github.com/Layr-Labs/eigenlayer-contracts/#deployments
Unless explicitly listed, only pages of the web/app assets in addition to the direct link are considered in-scope of the bug bounty program. Other subdomains are not considered as in-scope. However, for subdomain takeovers that lead to an impact on the in-scope asset, please refer to our page about Reported Subdomain Takeovers.
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.
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol) where the damage to users far exceeds the cost to attackers.MediumImpact
Websites and Applications
- 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 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
- 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
- Subdomain takeover without already-connected wallet interactionHighImpact
- Redirecting users to malicious websites (Open Redirect)MediumImpact
Out of Scope & Rules
These impacts are out of scope for this bug bounty program.
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
- Best practice recommendations
- Impacts from malicious upgrades to third party contracts utilized by EigenLayer
- Theoretical impacts without any proof or demonstration
- Impacts involving attacks requiring physical access to the victim device
- Impacts involving attacks requiring access to the local network of the victim
- Reflected plain text injection (e.g. url parameters, path, etc.)
- This does not exclude persistent plain text injection
- Any impacts involving self-XSS
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (e.g. logout CSRF)
- Impacts related to 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
- Impacts causing only the enumeration or confirmation of the existence of users or tenants
- Impacts caused by vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- Impacts that only require DDoS
- UX and UI impacts that do not materially disrupt use of the platform
- Impacts primarily caused by browser/plugin defects
- Leakage of non sensitive API keys (e.g. Etherscan, Infura, Alchemy, etc.)
- Any vulnerability exploit requiring browser bugs for exploitation (e.g. CSP bypass)
- SPF/DMARC misconfigured records
- Missing HTTP Headers without demonstrated impact
- Automated scanner reports without demonstrated impact
- UI/UX best practice recommendations
- Non-future-proof NFT rendering
The following activities are prohibited by this bug bounty program:
- 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