← Opportunities

Bug Bounty Policy | DFINITY

Funder
DFINITY Foundation · Internet Computer Bug Bounty Program 🟡 Some evidence
Type / status
other · open
Amount
0 – 50,000 USD
Deadline
rolling
“We are happy to thank everyone who submits valid reports which help us improve security.”
Ecosystems
internetcomputer
Categories
security
Tech stack
rustmotokotypescriptcandid
Apply
https://dfinity.org/bug-bounty/submit
Source
https://dfinity.org/bug-bounty
Fit
26% · weak fit · The Venture23 Aleo team has ZK and Rust expertise, which aligns with the security and tech stack, but they operate in the Aleo ecosystem rather than Internet Computer, making them an outsider to this specific funder.
Trust
57% · model self-report 95% · first seen 2026-09-28 · v1
Verified
2026-11-15 · page still up, no closing language

DFINITY offers a bug bounty program for security vulnerabilities in the Internet Computer Protocol and related components. Researchers can submit reports for issues in scope areas such as core protocol, governance, financial integrations, chain fusion, Internet Identity, developer tooling, infrastructure, wallets, and more. Rewards range from $0 to $50,000 based on severity, with payments made in ICP after KYC verification. Reports must be submitted via HackenProof with steps to reproduce and proof of concept.

Eligibility: Open to anyone who is not a current DFINITY employee or contractor, must use HackenProof for submissions, follow disclosure guidelines, and complete KYC verification for payment.

Pipeline

Override status:

Funder track record · does DFINITY Foundation actually pay grants?

🟡 Some payout evidence · 2 grantees found · last payout 2024-12-13 · checked 2026-11-02 · 0 forum reports, 6 web pages read

Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.

GranteeAmountDateEvidence
Copute—2024-12-13“Singaporean DePIN protocol Copute has secured a community grant from DFINITY Foundation” source
Momint$50,0002024-07-16“Momint, Africa's leading Web3 platform based in South Africa, has secured a $50,000 grant from the DFINITY Foundation” source

Trust breakdown (3/4 checkable facts verified)

SignalWeightResultNote
deadline0.350%rolling claimed but not stated
amount0.25100%figure appears in source
apply link0.075100%link in source
funder0.075100%named in source
source quality0.1550%social or search hit
model confidence0.195%model self-report

Fit breakdown (against the ORG_* profile)

SignalWeightResultNote
model fit0.540%model rated 40%
ecosystem overlap0.250%internetcomputer vs aleo
category overlap0.1517%security vs zk, privacy, infra, dev_tooling, security, interoperability
tech overlap0.133%rust, motoko, typescript, candid vs rust, leo, zk

Sources (1)

RoleDocumentFromFetched
primaryBug Bounty Policy | DFINITYWeb discovery: ecosystem sweep2026-09-28

History (1)

vChangedFields
12026-09-28created

Extracted text

# Internet Computer  
Bug Bounty Policy

This bug bounty program focuses on the Internet Computer Protocol (ICP), core Internet Computer components, and related products. To learn about rewards you could get, see the “Rewards” section. If you’re new to finding security bugs in ICP dapps, read the [security best practices](https://docs.internetcomputer.org/guides/security/overview/).

[Submit Bug Report](/bug-bounty/submit) See Scope and Targets

## Scope and Targets

For a bug to be considered for a bounty, it must be in the scope outlined in this section. If you found a bug that is not explicitly in scope, we encourage you to still submit it. It may still qualify for a bounty depending on DFINITY’s discretion and the attack’s impact.

*   [Core Internet Computer Protocol stack](#core-protocol)
*   [Governance: Network Nervous System and Service Nervous System](#governance)
*   [Financial Integrations](#financial-integrations)
*   [Chain Fusion and Cross-Chain Applications](#chain-fusion)
*   [Internet Identity: Self-Sovereign Single Sign-on Solution](#internet-identity)
*   [Developer Experience and Tooling: SDK, CDK, Motoko](#developer-experience)
*   [Internet Computer Infrastructure](#ic-infrastructure)
*   [Wallets](#wallets)
*   [Exchange Rate Canister](#exchange-rate)
*   [Internet Computer Dashboard](#dashboard)

### 🎯 Core Internet Computer Protocol Stack

The Internet Computer Protocol is a distributed protocol run by multiple nodes that constitute the Internet Computer network. It is structured into layers which are peer-to-peer, consensus, message routing, and execution. See [our protocol documentation and specs](https://docs.internetcomputer.org/references/ic-interface-spec/). In order to get a good overview of the Internet Computer and to get started see [our documentation](https://legacy.internetcomputer.org/howitworks/).

[The Internet Computer Protocol (ICP) GitHub Repository](https://github.com/dfinity/ic)

Some important components are the following, but protocol implementation spans across additional crates:

*   [execution](https://github.com/dfinity/ic/tree/master/rs/execution_environment), [system\_api](https://github.com/dfinity/ic/tree/master/rs/system_api), [canister\_sandbox](https://github.com/dfinity/ic/tree/master/rs/canister_sandbox) and [embedders](https://github.com/dfinity/ic/tree/master/rs/embedders): execution layer for wasm smart contracts
*   [consensus](https://github.com/dfinity/ic/tree/master/rs/consensus) and [orchestrator](https://github.com/dfinity/ic/tree/master/rs/orchestrator): consensus protocol implementation
*   [message routing](https://github.com/dfinity/ic/tree/master/rs/messaging) and [xnet](https://github.com/dfinity/ic/tree/master/rs/xnet): messaging layer implementation
*   [state\_manager](https://github.com/dfinity/ic/tree/master/rs/state_manager): state management
*   [p2p](https://github.com/dfinity/ic/tree/master/rs/p2p) and [http\_endpoints](https://github.com/dfinity/ic/tree/cc1792ad43e5bb7b826a987d2fdd540ea0d906bd/rs/http_endpoints): networking layer implementation
*   [http\_outcalls](https://github.com/dfinity/ic/tree/master/rs/https_outcalls): HTTP calls from canisters to Web 2.0
*   [crypto](https://github.com/dfinity/ic/tree/master/rs/crypto): implementation of core crypto, including threshold signatures

### 🎯 Governance: Network Nervous System and Service Nervous System

#### Network Nervous System (NNS)

All aspects of ICP behavior are governed by the community of enthusiasts and users through a democratic governance system called the [Network Nervous System (NNS)](https://learn.internetcomputer.org/hc/en-us/articles/33692645961236-NNS-Network-Nervous-System). A high-level introduction can be obtained from this [quick video](https://learn.internetcomputer.org/hc/en-us/articles/33692645961236-Overview).

*   [Network Nervous System (NNS) on GitHub](https://github.com/dfinity/ic/tree/master/rs/nns)
    *   Core canisters include NNS Root, NNS Governance, NNS CMC, NNS GTC (Genesis Token Canister), NNS lifeline canister
*   [Registry on GitHub](https://github.com/dfinity/ic/tree/master/rs/registry)

#### Service Nervous System (SNS)

ICP offers a framework to launch decentralized autonomous organizations (DAOs), called the [Service Nervous System (SNS)](https://learn.internetcomputer.org/hc/en-us/articles/34084394684564-SNS-Service-Nervous-System):

*   [Service Nervous System (SNS) on Github](https://github.com/dfinity/ic/tree/master/rs/sns)
    *   Core canisters include SNS Root, [SNS-W](https://github.com/dfinity/ic/tree/master/rs/nns/sns-wasm), SNS Governance, SNS Swap

#### Frontend applications

The [NNS front-end dapp](https://nns.ic0.app/) provides a user-friendly way to interact with the Internet Computer's governance system. It offers features such as logging in using Internet Identity, sending and receiving tokens, staking neurons, and viewing and voting on NNS and SNS proposals. See also the [NNS dapp tutorial](https://legacy.internetcomputer.org/docs/building-apps/governing-apps/nns/using-the-nns-dapp/nns-app-quickstart).

*   [Network Nervous System dapp on GitHub](https://github.com/dfinity/nns-dapp)
*   Domain: [https://nns.ic0.app/](https://nns.ic0.app/)

### 🎯 Financial Integrations

ICP provides ledger implementations for the ICP token according to the [ICRC standards](https://github.com/dfinity/ICRC-1):

*   [Ledgers on GitHub](https://github.com/dfinity/ic/tree/master/rs/ledger_suite), including archive and index canisters

Rosetta API provides applications that third parties (e.g. exchanges) can run to obtain ICP price data:

*   [Rosetta API on GitHub](https://github.com/dfinity/ic/tree/master/rs/rosetta-api)

### 🎯 Chain Fusion and Cross-Chain Applications

#### Chain-Key (ck) Tokens

These are ICRC compliant tokens that bring other assets, such as BTC or ETH to the ICP ecosystem. See also the [Chain Fusion page](https://legacy.internetcomputer.org/chainfusion).

*   Bitcoin
    *   [Bitcoin integration](https://github.com/dfinity/ic/tree/master/rs/bitcoin), including the [adapter](https://github.com/dfinity/ic/tree/master/rs/bitcoin/adapter), [docs](https://docs.internetcomputer.org/concepts/chain-fusion/bitcoin/)
    *   [ckBTC on GitHub](https://github.com/dfinity/ic/tree/master/rs/bitcoin/ckbtc) and the related [BTC checker](https://github.com/dfinity/ic/tree/master/rs/bitcoin/checker), [docs](https://legacy.internetcomputer.org/docs/current/developer-docs/multi-chain/chain-key-tokens/ckbtc/overview)
*   Ethereum:
    *   [ckETH and ckERC20 on GitHub](https://github.com/dfinity/ic/tree/master/rs/ethereum), [ckETH docs](https://legacy.internetcomputer.org/docs/current/developer-docs/multi-chain/chain-key-tokens/cketh/overview), [ckERC20 docs](https://legacy.internetcomputer.org/docs/current/developer-docs/multi-chain/chain-key-tokens/ckerc20/overview)
    *   [EVM RPC canister](https://github.com/dfinity/evm-rpc-canister) including the [client](https://github.com/dfinity/ic/tree/master/rs/ethereum/evm-rpc-client)

### 🎯 Internet Identity: Self-Sovereign Single Sign-on Solution

[Internet Identity](https://docs.internetcomputer.org/guides/authentication/internet-identity/) is an anonymous, tamperproof authentication framework on ICP and supports [passkey authentication](https://fidoalliance.org/passkeys/). Check out the [quickstart guide](https://legacy.internetcomputer.org/how-it-works/web-authentication-identity/) to Internet Identity and the following [video](https://www.youtube.com/watch?v=9eUTcCP_ELM).

*   [Internet Identity on GitHub](https://github.com/dfinity/internet-identity), [specification](https://github.com/dfinity/internet-identity/blob/main/docs/ii-spec.mdx)
*   Domain: [https://identity.ic0.app/](https://identity.ic0.app/)

### 🎯 Developer Experience and Tooling: SDK, CDK, Motoko

The documentation for tools and development kits to assist with development in ICP can be found [here](https://legacy.internetcomputer.org/docs/tutorials/developer-liftoff/level-1/1.2-dev-env). Motoko is a custom built, native language for ICP that simplifies the development of smart contract canisters.

Source code & domain:

*   [Motoko](https://github.com/dfinity/motoko) and [Motoko base library](https://github.com/dfinity/motoko-base) on GitHub
*   [IC Software Development Kit on GitHub](https://github.com/dfinity/sdk)
*   [Rust Canister Development Kit](https://github.com/dfinity/cdk-rs)
*   Agents for clients to interact with ICP:
    *   [JavaScript Agent on GitHub](https://github.com/dfinity/agent-js)
    *   [Rust Agent on GitHub](https://github.com/dfinity/agent-rs)
*   [Candid IDL on GitHub](https://github.com/dfinity/candid)
*   [Cycles Ledger on GitHub](https://github.com/dfinity/cycles-ledger)
*   [Quill governance toolkit on GitHub](https://github.com/dfinity/quill)

### 🎯 Internet Computer Infrastructure

#### Node Operating Systems

The node software runs on the virtual machine termed 'GuestOS' that in turn runs on 'HostOS'. In addition to these OSes, the boundary node systems have their own operating system 'Boundary-guestOS'. Finally, the 'SetupOS' is used to install and set up a node.

*   [Operating Systems on GitHub](https://github.com/dfinity/ic/tree/master/ic-os)

#### Edge Infrastructure: HTTP Gateway and API Boundary Nodes

The HTTP gateways and the API boundary nodes are major ICP infrastructure components. They sit on the perimeter and act as a gateway to the Internet Computer platform. Here is the list of components:

*   [HTTP gateway on GitHub](https://github.com/dfinity/ic-gateway)
*   [Boundary nodes on GitHub](https://github.com/dfinity/ic/tree/master/rs/boundary_node)
*   [Boundary node OS on GitHub](https://github.com/dfinity/ic/tree/master/ic-os/boundary-guestos)
*   Domains: [boundary.ic0.app](https://boundary.ic0.app/), [boundary.dfinity.network](https://boundary.dfinity.network/)
    *   boundary.dfinity.network: main load balancer
    *   ic0.app, icp0.app: used for [ICP api calls](https://docs.internetcomputer.org/references/ic-interface-spec/https-interface/) and as HTTP gateway:
        *   With HTTP asset certification <canister-id>.ic0.app
        *   Without HTTP asset certification <canister-id>.raw.ic0.app
    *   icp-api.io used for [ICP api calls](https://docs.internetcomputer.org/references/ic-interface-spec/https-interface/) (no HTTP gateway)

#### Other infrastructure

In addition to the boundary nodes there are additional infrastructure assets that support the operations of the Internet Computer. Here is the list of the domains:

*   dfinity.network
*   dfinity.systems

### 🎯 Wallets

#### Oisy

Oisy is a new browser-based, network-custodial and multi-chain wallet powered by Internet Computer's chain fusion technology.

*   [Oisy on GitHub](https://github.com/dfinity/oisy-wallet)
*   [Chain Fusion Signer on GitHub](https://github.com/dfinity/chain-fusion-signer)
*   Domain: [https://oisy.com/](https://oisy.com/)

#### Orbit

Orbit is a non-custodial platform for secure digital asset and smart contract management on the Internet Computer. It enables teams to define approval workflows, enforce governance policies, and manage assets with flexibility and transparency.

*   [Orbit on GitHub](https://github.com/dfinity/orbit)
*   Domain: [https://orbit.global](https://orbit.global)

### 🎯 Exchange Rate Canister

The exchange rate canister provides an oracle service for cryptocurrency and fiat currency exchange rates. It interacts with all data sources using the [HTTPS outcalls](https://docs.internetcomputer.org/concepts/https-outcalls/) feature.

*   [Exchange rate canister on GitHub](https://github.com/dfinity/exchange-rate-canister)

### 🎯 Internet Computer Dashboard

The internet computer dashboard is a web application that provides visibility into the Internet Computer. It provides metrics and information about governance, network (subnets, data centers, nodes), Chain Fusion, etc.

*   Domain: [https://dashboard.internetcomputer.org/](https://dashboard.internetcomputer.org/)

### Out of scope

All public websites (not explicitly listed in scope below) and 3rd party code is out of scope for this bug bounty program. You can report issues but we don’t provide rewards.

Network-level DoS and DDoS is out of scope. Network-level misconfigurations or application or platform-level DoS issues (especially crashes) may qualify for a bounty depending on DFINITY’s discretion and the attack’s impact. We ask researchers not to perform DoS attacks on mainnet and production deployments. This will disqualify you from a bounty and from the bug bounty program entirely. Consider using local setups (e.g. using DFX) to demonstrate crashes, or reach out to us and we can support you to reproduce exploits.

[Submit informational bug](/bug-bounty/submit)

### Program Rules

*   Do not use off the shelf dynamic scanners such as DAST tools on production systems.
*   Make every effort not to damage or restrict the availability of products, services, and infrastructure
*   Avoid compromising any personal data, interruption, or degradation of any service
*   Don't access or modify other user data, localize all tests to your accounts
*   Perform testing only within the scope
*   Don't exploit any DoS/DDoS vulnerabilities or social engineering attacks
*   Don't break any law

### Disclosure Guidelines

*   Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without explicit consent from the organization.
*   Act responsibly and in good faith during the disclosure process.

### Eligibility and Coordinated Disclosure

We are happy to thank everyone who submits valid reports which help us improve security. However, only those that meet the following eligibility requirements may receive a monetary reward:

*   Abide by the program rules and disclosure guidelines.
*   Ensure that the potential security bug you are reporting is in scope as specified in the Scope & Targets section below.
*   Any vulnerability found must be reported as soon as possible after discovery through hackenproof.com. Reports sent to DFINITY email addresses are not monitored and will not receive a response.
*   You must send a clear textual description of the report along with steps to reproduce the issue, including attachments such as screenshots or proof of concept code as necessary.
*   While AI-assisted tools can be very helpful and are encouraged to discover relevant bugs, their use in identifying vulnerabilities or preparing reports must be clearly disclosed. Keep reports brief, clear, and focused and avoid excessively long or repetitive AI-generated submissions. To ensure accuracy and quality, all participants are expected to personally verify any findings produced with the help of AI tools before submitting them. Any reports not meeting these standards may be rejected.
*   You must not be a current employee of DFINITY or one of its contractors.
*   Only use the email address under which you registered your HackenProof account.
*   Do not engage in social engineering techniques or spear-phishing campaigns. Do not cause any harm to the data or the system.
*   Duplicate reports and closely related submissions will be dealt with on a case-by-case basis. If the submissions are determined to be genuine they may be rewarded based on a lower rewards scale.
*   In case that your finding is valid you might be asked for extra KYC verification to proceed with payments

## Incident Handling

The Dfinity Foundation will respond to a submission within 72 hours. All valid security bugs will be handled in accordance with the [Security Patch Policy](https://dashboard.internetcomputer.org/proposal/48792) and will trigger an internal incident response process. We will keep you updated and work with you throughout the process. Once the security bug has been handled, a communication will be made to the community describing the incident where we will provide an acknowledgment for your efforts and soon follow it up with the rewards.

![Incident handling process illustration](/img/incident-handling.svg)

## Rewards

#### CRITICAL

$10,000 - $50,000

The attack is easy to perform without special privileges, at a low cost and has a severe global impact.

* * *

##### Example

Disclosure of subnet key shares, compromise of the integrity of the consensus process such as the insertion of an arbitrary block into the blockchain, remote code execution (RCE) in internal networks, memory underflow/overflow issues resulting in theft or illegal minting of exorbitant ( > $1M) amount of ICPs/Cycles.

#### HIGH

$2,000 - $10,000

The attack is relatively straightforward but may have additional constraints that may affect the ease or cost of the attack to a certain degree but still with a significant impact.

* * *

##### Example

A vulnerability that induces unauthorized access to neurons (access control bypass) but requires significant amount of work per neuron, memory corruption of canisters resulting in loss of integrity but constrained by a limiting factor such as being exploitable only on canisters with certain pre-existing properties.

#### MEDIUM

$200 - $2,000

The attack is difficult to perform, requires significant technical know-how and cost or the target may have to satisfy strict requirements in order to make a significant impact. Also, attacks that are simpler to perform but with moderate impact fall under this category.

* * *

##### Example

Memory corruption resulting in a one-time crash of a single replica on an application subnet, a client-side vulnerability that allows for the theft of individual session keys with access to limited funds, an issue affecting subnet availability but requires control of a node or boundary node.

#### LOW

$0

Attacks that are very difficult to perform or have a minor impact fall under this category.

* * *

##### Example

A bug resulting in an attacker controlling what is displayed to the user without affecting the server side data, UI redress, a bug that is not demonstrably exploitable but could be exploitable with more research.

#### INFORMATIONAL

Anything that doesn't fit the other ratings. You can report these issues but we don't provide rewards.

## Rewards Payment Process

1.  Obtain an ICP wallet address
2.  Whitelist your email
3.  Submit your KYC application

1.  First, obtain an ICP wallet address. You may use any valid ICP wallet address that best fits your needs and convenience. Below are some custody options you can choose from to obtain a KYC-verified ICP wallet address.
    *   Self-Custody:
        *   [NNS dapp](https://nns.ic0.app/) \- [how to get started](https://medium.com/dfinity/getting-started-on-the-internet-computers-network-nervous-system-app-wallet-61ecf111ea11)
        *   [Oisy](https://oisy.com/) \- a browser-based, network-custodial and multi-chain wallet
        *   [Quill](https://github.com/dfinity/quill) \- a minimalistic ledger and governance toolkit for cold wallets.
    *   Third Party Custody Solutions
        *   [Coinbase Pro/Retail](https://pro.coinbase.com/)
        *   [Klever](https://klever.io/)
        *   [Plug wallet](https://plugwallet.ooo/)
        *   [Stoic wallet](https://www.stoicwallet.com/)
        *   [Coinbase Custody](https://www.coinbase.com/custody)
2.  Once your ICP wallet address is ready, send the address along with the email address you plan to associate your account with **before** starting the KYC process. The provided email address will be whitelisted on the KYC website within approximately 3 working days.
3.  You will receive an email notification once your email has been whitelisted. [Submit your KYC application](https://kyc.dfinity.org/) on the [KYC DFINITY page](https://kyc.dfinity.org) by clicking on 'Other' and entering the email address you provided. You will receive a unique link to begin the verification process. The KYC process will be performed by a third party. The only information that the DFINITY Foundation receives is your email address and ICP wallet address.

Ensure that, at every stage of the onboarding process, your wallet address and associated email address are entered correctly to avoid any delay. As a reminder, DFINITY is not responsible for your asset custody nor will it be held accountable for any loss of your ICP distributed to the ICP wallet address you have provided.

If you have any questions regarding your KYC application or obtaining your ICP wallet address, please contact [DFINITY Support](https://support.dfinity.org/hc/en-us) .

## Submit Bug Report

[Submit bug report](/bug-bounty/submit)