Decentralized Security, Community-Powered Recon

Bounty Overview Rewards by Severity Assets in Scope In-scope Vulnerabilities Out-of-scope Vulnerabilities Program Rules FAQs

Coreum

Smart Contract Platform

Infrastructure

DEX

Max Payout

$25,000

Project Overview

Coreum is a next-generation Layer 1 blockchain designed to overcome the limitations of legacy networks. By offering built-in, on-chain solutions and deterministic transaction processing, Coreum delivers a fast, secure, low-cost, and environmentally sustainable infrastructure. Its architecture supports a wide range of decentralized applications, making it a robust foundation for scalable Web3 innovation.

Rewards by Severity

Program Overview Coreum Network operates a security-focused bug bounty program to identify and address vulnerabilities across its blockchain infrastructure. The program encourages responsible disclosure from the security research community to ensure a safe and robust user environment.

Reward Structure All submissions are evaluated under a 4-tier severity model, with rewards determined by the severity of the vulnerability and its impact on in-scope system components. Submissions that expose critical flaws in Coreum’s smart contracts or blockchain logic qualify for higher-tier rewards, while lower-tier rewards apply to moderate and minor issues with lower security impact.

Submission Requirements All bug reports must include a valid proof of concept (PoC) and step-by-step instructions to reproduce the issue, with demonstrable impact on an asset within the defined program scope. Written explanations or theoretical claims without accompanying code are not accepted.

Payouts Bounties are denominated in USD but paid out in CORE, Coreum Network’s native token. All rewards are issued by the Coreum team after successful report validation and KYC completion.

Blockchain/DTL

The bounty will be paid out in CORE

Assets In-Scope

Target

Severity

Name

https://github.com/CoreumFoundation/coreum

Blockchain/DTL

Coreum source code

https://www.coreum.com

Application/Web

Website

https://docs.coreum.dev

Application/Web

Website

https://explorer.coreum.com/coreum

Application/Web

Website

In-Scope Vulnerabilities

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 table.

Blockchain/DTL

Critical

Network not being able to confirm new transactions (Total network shutdown)

Unintended permanent chain split requiring hard fork

Permanent freezing of funds(fix requires hard fork)

Transaction/consensus manipulation

Significant loss of funds

Unauthorized token minting and sending

Major

Transient consensus failures

Bad/incorrect usage of cryptography primitives

Validator selection set manipulation

Unauthorized token Burning and Freezing

Medium

High compute consumption by validator/mining nodes

Vulnerability in RPC API (except via DDoS attack)

Attacks against thin clients

Unhandled on-chain errors affecting a user corner case

A remote call that crashes a Coreum Node

Any vulnerabilities that give exploits or misconfiguration of https://www.coreum.co

Any vulnerabilities that give exploits or misconfiguration of https://docs.coreum.dev

Any vulnerabilities that give exploits or misconfiguration of https://explorer.coreum.com/coreum

Low

Underpricing transaction fees relative to computation time

Griefing (e.g. triggering abnormally high gas fees for everyone or abnormal cpu consumption for validator/mining nodes)

Out-Of-Scope Vulnerabilities

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

Vulnerabilities that have already been exploited
Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.

Blockchain/DTL

Centralization risks

Best practice critiques

Impacts caused by attacks requiring access to leaked keys/credentials; Mentions of secrets; access tokens; API keys; private keys etc. in Github will be considered out of scope without proof that they are in-use in production

Attacks that the reporter has already exploited themselves leading to damage

Test and Mock files

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

Lack of liquidity

Sybil attacks

Phishing attacks or scams

Previously known vulnerabilities in Tendermint(CometBFT) and or/any other fork of these

Previously known vulnerabilities in Cosmos-SDK and or/any other fork of these

Previously known vulnerabilities in CosmWasm and or/any other fork of these

Previously known vulnerabilities in IBC and or/any other fork of these

Any other vulnerabilities that come from Third-Party services and SDKs

Public Zero-day vulnerabilities

Denial of service (DoS) / Distributed Denial of Service(DDOS) / Spamming

Email services configuration DKIM and SPF records

Any issue on the issue tracker: https://github.com/CoreumFoundation/coreum/issues

Any issue found on open pull requests: https://github.com/CoreumFoundation/coreum/pulls

The bridge

UI bugs

Program Rules

Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue - the issue will not be eligible for a reward.
Submit one vulnerability per report - unless you need to chain vulnerabilities to provide impact.
When duplicates occur we only award the first report that was received (provided that it can be fully reproduced).
Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
Make a good faith effort to avoid privacy violations - destruction of data - and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
Do not attempt to conduct post-exploitation including modification or destruction of data - and interruption or degradation of services.
Do not attempt to perform brute-force attacks or denial-of-service attacks.
Do not attempt to target employees or customers including social engineering attacks - phishing attacks or physical attacks.
Whitehats are highly encouraged to review any potential subdomains and what specific port(s) are in scope. Even though the domain may be the same different ports may point to different assets. If whitehats can demonstrate a critical impact on code in production for an asset not in scope
Coreum encourages you to submit your bug report with the "Out of scope but critical" mark.

The following activities are prohibited by this bug bounty program:

Any testing with mainnet, testnet, and devnet
Automated testing of services that generate significant amounts of traffic.
Public disclosure of an unpatched vulnerability in an embargoed bounty.
Social engineering (e.g. phishing, vishing, smishing) of any kind.

FAQs

How do I search for active bounties?

A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.

How do I submit a bounty?

To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.

Who do I contact if I'm having trouble with my bug report submission?

You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.

I submitted my bug report. What now?

Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.

How is KYC handled?

CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.

Why was my bug report submission rejected?

A description of dismissal will be available for any bug bounty that is rejected.

The project is being slow responding to my bug report. What are their required response times / SLAs?

There can be multiple bug bounty submissions therefore there might be some delay in process times.

How do payouts work?

Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.

Bounty Highlights

Assets in Scope4

Live SinceJul 1, 2023

Last Updated2mo 18d ago

Funds Reserved$500,000

Max Payout$25,000

Skynet Score

91.29

KYC

Required

PoC

Required

View on Skynet