Immunefi Bug Bounty

Immunefi is the leading bug bounty and security services platform for Web3, guarding over $25 billion in user funds across crypto projects. Immunefi hosts bug bounties for blockchain projects across all chains and networks by providing a forum bringing builders and hackers together, enabling hackers to report bugs privately and responsibly for projects to fix vulnerabilities securely.

LEVEL Bug Bounty

Rewards by Threat Level

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. 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 Proof-of-Concept (PoC) and an end-effect that impacts an Asset in Scope to be considered for a reward. Bug reports must include an executable PoC in order to prove the impact. Exceptions may be made in cases where the vulnerability is objectively evident by simply mentioning its existence and location. Though please note, in such a case, the bug reporter may be required to provide a PoC at any point in time.

Reward Payment Terms

Smart Contract

Websites and Applications

Payouts are handled by the LEVEL team directly and are denominated in USD, but payouts are distributed in LVL tokens. The bug bounty program has the following hard caps:

  • Smart Contracts: $1,000,000

  • Websites and Applications: $10,000

In the event that multiple bug reports are submitted that exceed this amount, the rewards will be provided on a first come first served basis.

Assets in Scope

Smart Contracts

Websites and Applications

The entire LEVEL codebase can be found at https://github.com/level-fi. The scope of this bug bounty program is restricted to Assets in Scope, shown above.

For reference purposes, the public testnet can be found at https://test.level.finance/. Please note, program rules prohibit testing on the public testnet.

In the case that an impact is found that does not fit into the Assets in Scope but can be found below in the Impacts in Scope, you are encouraged to submit it for consideration by the team.

Impacts in Scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the Assets in Scope.

Smart Contract

Websites and Applications

Out of Scope & Rules

The following vulnerabilities are excluded from the rewards of this bug bounty program:

All Categories

  • Attacks that the reporter has already exploited themselves, leading to damage

  • Attacks requiring access to leaked keys/credentials

  • 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

  • Broken link hijacking is out of scope

Smart Contracts and Blockchain/DLT

  • Basic economic governance attacks (e.g. 51% attack)

  • Lack of liquidity

  • Best practice critiques

  • Sybil attacks

  • Centralization risks

Websites and Applications

  • Theoretical vulnerabilities without any proof or demonstration

  • Content spoofing/Plain text injection ex: url parameters, path, etc.

  • This does not exclude reflected HTML injection with or without javascript

  • This does not exclude persistent plain text injection

  • Self-XSS

  • Captcha bypass using OCR

  • CSRF with no state modifying security impact (ex: logout CSRF)

  • 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

  • Vulnerabilities used only to enumerate or confirm the existence of users or tenants

  • Vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows

  • URL redirects (unless combined with another vulnerability to produce a more severe vulnerability)

  • Lack of SSL/TLS best practices

  • Attacks involving DDoS

  • SPF records for email domains

  • Feature requests

  • Issues related to the front-end without concrete impact and PoC

  • Best practices issues without concrete impact and PoC

  • Vulnerabilities primarily caused by browser/plugin defects

  • Leakage of non-sensitive API keys ex: Etherscan, Infura, Alchemy, etc.

  • Any vulnerability exploits requiring browser bugs for exploitation. ex: CSP bypass

The following activities are prohibited by this bug bounty program:

  • Any testing with mainnet or public testnet contracts: all testing should be done on local-forks of either public testnet or mainnet

  • Any testing with pricing oracles or third-party smart contracts

  • Attempted 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

  • Automated testing of services that generates significant amounts of traffic

  • Public disclosure of an unpatched vulnerability in an embargoed bounty

PreviousSecurity and AuditsNextPrice Oracles

Last updated