LayerZero is an omnichain interoperability protocol that allows developers to seamlessly interact with contracts across blockchains.
Triaged by Immunefi
PoC Required
KYC required
Arbitration enabled
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
If an impact can be caused to any other asset managed by LayerZero that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. The vulnerability will then be evaluated by LayerZero Labs in good faith to determine where it would fall on the vulnerability scale.
Exploits resulting in the permanent locking or theft of user funds
Permanent DoS attacks (excluding volumetric attacks)
Any governance voting result manipulation
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Out of scope
- LayerZero Offchain Infrastructure
- Sybil Attacks
- Impacts to OApps themselves as a result of their own misconfiguration (including but not limited to e.g. configuring bad libraries, verifier networks, executors, etc).
- Reports regarding bugs that LayerZero was previously aware of are not eligible for a reward
- Dependencies & Third Party Code
- Temporary impacts resulting from configuration adjustment race-conditions
Smart Contract specific
- 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
All categories
- 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 (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- 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
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers