External Adapters component of the Chainlink stack

The following are considered out of scope for the program:

  - Any files in a dev folder
  - Any contract with a `typeAndVersion` string which contains `-dev`
  - Any files with XXX in their name
  - Any *.smartcontract.com assets
  - Any test code

Also, for any file to be in scope, it has to be part of a release, not including pre-releases.

If an impact can be caused to any other asset managed by Chainlink 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 consideration by the project.

Chainlink is the industry-standard Web3 services platform. It has enabled trillions of dollars in transaction volume across DeFi, on-chain finance, gaming, NFTs, and other major industries. As the leading decentralized oracle network, Chainlink empowers developers to build feature-rich Web3 applications with seamless access to real-world data and off-chain computation across any blockchain.

Any governance voting result manipulation

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

Permanent freezing of funds

Predictable or manipulable RNG that results in abuse of downstream services

Protocol insolvency

Misreporting of prices and/or data

RMN bypass

Execute arbitrary system commands

Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys

Injecting code that results in malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions

Temporary freezing of tokens used in Chainlink protocols for at least two (2) blocks

Theft of protocol revenue

Rate limit violations

Delaying delivery of oracle responses, including randomness, unrelated to congestion of the underlying blockchain

Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc

Improperly disclosing confidential user information such as email address, phone number, physical address, etc

Taking down the application/website with methods other than DDoS

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

Unbounded gas consumption

Loss of protocol revenue (i.e skipping all or part of protocol fees)

Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as changing the first/last name of user, or en/disabling notification

Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site data

Subdomain takeover

Smart contract fails to deliver expected return(s) but doesn’t result in loss of value

Changing details of other users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction such as iframing leading to modifying the backend/browser state (demonstrate impact with PoC)

Redirecting users to malicious websites (open redirect)

Temporarily disabling user to access target site, such as locking up the victim from login, cookie bombing, etc

Only the following impacts are accepted within this bug bounty program. All other impacts are out of scope, even if they affect an in scope asset.

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/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 Smart Contracts bug reports require a proof of concept (PoC) and a suggestion for a fix to be eligible for a reward. All Websites and Applications bug reports must come with a PoC with an end-effect impacting an asset in scope in order to be considered for a reward. Explanations and statements are not accepted as PoCs and code is required.

Rewards for Critical Smart Contract vulnerabilities are at the sole and exclusive discretion of Chainlink Labs, with maximum reward of USD $3,000,000.

Specific reward amounts are determined based on a number of factors, such as the impact of proposed issues, ease of exploitability, and how likely the exploit conditions might occur.

Any supplementary reward beyond the minimum for the assigned criticality rating is at the discretion of Chainlink Labs.

__KYC requirement__

To ensure compliance, Chainlink Labs requires Know-Your-Customer (KYC) information to be provided for all bug bounty reporters submitting a report and requesting a reward. 

The information required:

  - Color copy of passport
    - Full Legal Name (First, middle, and last, plus any prefix, and/or suffix)

  - Proof of current address (either a redacted bank statement with your address or a recent utility bill with your name, address, and issuer of the bill)

  - If you are a U.S. citizen, permanent resident, partnership, LLC, corporation, estate or trust, please send a filled-out and signed W-9 ([https://www.irs.gov/pub/irs-pdf/fw9.pdf](https://www.irs.gov/pub/irs-pdf/fw9.pdf))

  - If you are not a U.S. citizen or permanent resident, please send a filled-out and signed W-8BEN for individual and W-8 BEN-E for entities ([https://www.irs.gov/pub/irs-pdf/fw8ben.pdf](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf); [https://www.irs.gov/pub/irs-pdf/fw8bene.pdf](https://www.irs.gov/pub/irs-pdf/fw8bene.pdf)), and provide statement to certify that all services are performed outside of the U.S. 

  - Ethereum Wallet Address (for transfer of payment)

All bug bounty reporters must pass the Office of Foreign Asset Control (OFAC) Specially Designated Nationals And Blocked Persons List (SDN) list screening. Rewards cannot be paid out if reporters are on the OFAC SDN list.

The collection and review of this information will be handled by the __Chainlink Labs__ team directly.

Payouts are handled by the __Chainlink Labs__ team directly, denominated in __USD__, and sent in __Ethereum (ETH)__ or __USD Coin (USDC)__.

__Feasibility Requirement and Limitations__

Chainlink will take the feasibility of an attack into consideration when determining if and how much a reported issue receives as a bounty. More information on feasibility limitations can be found under [Immunefi’s Feasibility Standards](https://immunefisupport.zendesk.com/hc/en-us/articles/16913132495377-Feasibility-Limitation-Standards).

__Repeatable Attacks__

In the event a report applies to multiple contracts or can be triggered multiple times, if a contract or product can be paused (either through on or off-chain means) only the impact of the first usage will be considered. If a product is not pausable such that there is no realistic way to prevent repeated usage of the attack, the entire amount at risk will be considered when evaluating impact.

Chainlink

Resources & Documentation