All smart contracts in the “contracts” directory are included in the bug bounty, except those under “contracts/mocks”, which are testing artifacts, and those under “contracts/vendor”.

As the premier crypto cybersecurity technology and services company, we’ve built OpenZeppelin Contracts with our best [security practices](https://contracts.openzeppelin.com/security).

Direct theft of user funds, whether at-rest or in-motion, other than unclaimed yield

Access control is bypassed, including privilege escalation

Governance voting result manipulation

Permanent freezing of funds

Permanent denial of service (smart contract is made unable to operate)

Theft of unclaimed yield / Permanent freezing of unclaimed yield - Impact severity is determined by potential yield lost

Temporary freezing of funds - Impact severity depends on funds at risk

Smart contract unable to operate due to lack of token funds

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Contract fails to deliver promised returns, but doesn't lose value

Temporary denial of service (smart contract is made unable to operate for one block, functionality is restored in the next block)

Invalid events are emitted, potentially confusing indexers (internal storage is unaffected)

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.3](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-3/). This is a simplified 5-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. 

The rewards stated here are additive to any existing bug bounty programs hosted by projects that are currently using OpenZeppelin contracts. 

Bounty rewards are given according to an impact/likelihood [matrix for assessing threat levels.](https://raw.githubusercontent.com/OpenZeppelin/immunefi-assets/main/impact-likelihood-matrix.png) Each issue is assessed considering the likelihood of the vulnerability being successfully exploited and the expected impact in scope to a single instance of the affected smart contract. Note that, as can be seen in the matrix, if the impact is Critical then the threat is always Critical, for other impacts the maximum reduction is one level only if the likelihood is low, and if the likelihood is high then the threat is increased one level above the impact. 

__Proof of Concept (PoC) Requirements__

A PoC compliant with [Immunefi PoC Guidelines and Rules](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules) is required for the following severity levels:
- Smart Contract: Critical
- Smart Contract: High

Bugs introduced by a release candidate version and reported during the review period, the dates for which will be declared by OpenZeppelin on each release, will receive a 50% bonus.

Payouts are handled by the __OpenZeppelin__ team directly and are denominated in USD. However, payouts are done in __ETH__ or __USDC__.

OpenZeppelin

Resources & Documentation