Rules

Immunefi has a set of rules that govern project and whitehat participation on its bug bounty platform and interaction with Immunefi-run spaces and team. These rules exist in addition to the rules that are listed on each bug bounty program page.

Violation of these rules can result in a temporary suspension or permanent ban from the Immunefi platform at the sole discretion of the Immunefi team.

For whitehats, this may also result in: 1) forfeiture and loss of access to bug reports, and 2) zero payout.

For projects, this may also result in: 1) being removed from the Immunefi platform, and 2) publication of this removal in the case of SLA breakage.

Please note that Immunefi has no tolerance for spam/low-quality/incomplete bug reports, beg bounty behavior, misrepresentation of assets and severity, and refusal to pay whitehats.

These rules can be changed at any time.

Prohibited Behavior for Whitehats

  • Any testing with mainnet or public testnet contracts. Testing on mainnet or public testnet is grounds for an immediate and permanent ban
  • Misrepresenting assets in scope: claiming that a bug report impacts/targets an asset in scope when it does not
  • Misrepresenting severity: claiming that a bug report is critical when it clearly is not
  • Misrepresenting impacts: selecting impacts that do not actually apply to your bug report
  • Automated testing of services that generates significant amounts of traffic
  • Exploiting/attacking or threatening to exploit/attack a project on Immunefi - see this article for Immunefi Proof of Concept (PoC) rules
  • Whitehacking with intent to save user or protocol funds without the express written consent of the project in the Immunefi Dashboard.
  • Attempting phishing or other social engineering attacks against Immunefi and/or projects on Immunefi
  • Contacting non-support staff at Immunefi about your bug report
  • Harassment, i.e., excessive, abusive, or bad faith communication
  • 'Beg bounty' behavior, i.e. begging for a bounty reward that is not owed to the whitehat based on the terms of the bug bounty program
  • Requesting gas fees from Immunefi or projects
  • Disputing a bug report in the dashboard once it has been paid or marked as closed, with the exception of requesting mediation
  • Advertising or promotion of services
  • Attacks based on personal characteristics
  • Impersonation of other whitehats
  • Obscene or extremely offensive usernames
  • Threats of violence
  • Threatening to publish or publishing people’s personal information without their consent
  • Extortion/blackmail or threats of extortion/blackmail
  • Posting illegal content
  • Reporting a bug that has already been publicly disclosed
  • Creating multiple accounts on the Immunefi platform
  • Publicly disclosing a bug report--or even the existence of a bug report for a specific project--before it has been fixed and paid
  • Failing to abide by the Responsible Publication Policy categories set by projects, which determines what whitehats are allowed to publish about their bug reports
  • Publicly posting screenshots from your Immunefi bug reports, unless it is a screenshot of amount rewarded
  • Placeholder bug submissions, i.e., bugs that have a vague title, very few details, and no reproducible steps
  • Submitting a bug report that is not substantially your own (co-submitting with another hacker with their consent is permitted)
  • Submitting duplicates of your original report to the same project to claim additional rewards
  • Submitting spam/very low-quality bug reports and submitting information through our platform that is not a bug report
  • Submitting a bug report in a language other than English
  • Submitting a bug report with no PoC or an incomplete PoC if it is required by the project's bug bounty program - see this article for Immunefi Proof of Concept (PoC) rules
  • Failing to provide KYC information necessary for a bug report payment within a reasonable length of time. Failure to do so may result in forfeiture of payment at Immunefi's communication and discretion
  • Providing inauthentic KYC information
  • Routing around Immunefi and communicating with a project directly - negotiations outside of the Immunefi dashboard are considered invalid
  • Submitting bugs via email or any channel other than the Immunefi platform
  • Submitting AI-generated/automated scanner bug reports
  • Submitting fixes to a project's repository without their express consent
  • Unauthorized disclosure or access of sensitive information beyond what is necessary to submit the report
  • Mediation request abuse
  • Promoting any of the behavior listed above

Prohibited Behavior for Projects

  • Mediation request abuse
  • Abusing the "no fix, no pay" rule by stealth fixing the bug later without providing full payment to the whitehat
  • Routing around Immunefi and communicating with a whitehat directly - negotiations outside of the Immunefi dashboard are considered invalid
  • Claiming a bug report is a known or duplicate issue without clear evidence
  • Paying whitehats who submit bug reports via Immunefi outside of Immunefi
  • Publicly disclosing a bug report before you have both fixed the issue and paid the whitehat
  • Soliciting whitehats on Immunefi for commercial projects or private bug bounty programs
  • Attacks based on personal characteristics
  • Bad faith communication
  • Closing a report without providing detailed information and/or evidence as to why it should be closed
  • Promoting any of the behavior listed above
  • Refusing to provide whitehats or Immunefi with necessary information about their project for invoicing purposes if that information is available
  • Breaking SLAs regarding responsiveness and bug report resolution

Behavioral Code

  • Be ethical
  • Be respectful and considerate
  • Be professional
  • Be patient
  • Be privacy conscious

Scope and Enforcement

The team will take all reasonable actions to ensure the successful execution of Immunefi's mission and the maximum effectiveness of the project.

All material in official project spaces is subject to the rules, and as such, can be deleted, modified, or rejected by the team if it is found to be in violation of the rules. In repeated or severe cases, the team may exclude users from the Immunefi bug bounty platform and/or its project spaces on a temporary or permanent basis.