Decentralized Security, Community-Powered Recon

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

Qubic

Web3

Token

Layer 1

Max Payout

$0.13

Project Overview

Qubic runs a Bug Bounty program for responsible disclosure of vulnerabilities in official repositories, public APIs, and declared smart contracts. Eligible reports are rewarded based on severity.

What we expect

Report vulnerabilities that affect confidentiality, integrity, or availability of Qubic software, APIs, wallets, node infrastructure, or smart-contract integrations.
Provide complete, reproducible reports including a proof-of-concept (PoC) and an explanation of impact.

Rewards

Rewards are based on severity and real-world impact. Example categories:
- Critical: fund exfiltration or full chain compromise — highest reward.
- High: remote code execution, private key exposure — large reward.
- Medium: privilege escalation, significant information disclosure — medium reward.
- Low: minor UI issues or low-impact information leaks — small reward.
Exact payouts are assigned case-by-case according to impact scoring.

How to report

Submit report via the bug-bounty portal.
Required report contents: brief summary, affected component/URL, reproduction steps, PoC, assessed impact, suggested remediation.
Acknowledgement of receipt will be sent within 72 hours. Status updates will be provided during triage and remediation. Disclosure policy
Do not publicly disclose vulnerabilities before Qubic provides a coordinated disclosure timeline or a fix is released.
Qubic grants legal Safe Harbor for good-faith security research conducted within the rules defined in this policy.

Mobile Application: Out of Scope Description: Best practice recommendations, Absence of client-side security measures (e.g., root/jailbreak detection, certificate pinning), Bypass of client-side measures, Attacks requiring rooted/jailbroken device, Attacks requiring the user to install third-party applications, Attacks requiring physical access to a user's device, Use of insecure functions in the binary without a confirmed exploit, Exposure of non-sensitive API keys, Non-Sensitive Data Disclosure, Previously known vulnerable libraries without a working Proof of Concept, Application allows installation on deprecated Android/iOS versions, Obfuscated Code

Rewards by Severity

Web Application

Blockchain

The bounty will be paid out in QUBIC

Assets In-Scope

Target

Severity

Name

https://github.com/qubic/core

Blockchain

Qubic Core

https://github.com/qubic/qiner

Blockchain

Qubic Reference Miner

https://github.com/qubic/qubic-cli

Blockchain

Qubic Core Client

http://api.qubic.org

Web Application

Qubic API

http://rpc.qubic.org

Web Application

Qubic RPC

https://github.com/qubic/ts-library

Web Application

Qubic Typescript Library

http://wallet.qubic.org

Web Application

Qubic Wallet

https://play.google.com/store/apps/details?id=org.qubic.wallet&hl=en_US

Mobile Application

Qubic Wallet Android App

https://apps.apple.com/us/app/qubic-wallet/id6502265811

Mobile Application

Qubic Wallet iOS App

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.

Web Application

Critical

Remote code execution enabling attackers to compromise the entire system

Direct theft of user and project's assets(e.g. NFTs; tokens)

Unauthorized access allowing full control over user accounts or wallets

Access to sensitive internal data (private keys; database and server credentials)

Unauthorized alteration of NFT Metadata

Subdomain(with already-connected wallet) takeover or availability disruption of critical assets (e.g. NFT URI; RPC server)

Major

Sensitive user data disclosed for a large amount of users (p.e. physical address; email; phone number)

Stored Cross-Site Scripting (XSS) without limitations

Access sensitive data from the database through SQL injection

Bypass of essential authentication mechanisms granting administrative privileges

Unauthorized access to functions that modify sensitive user or application data

Server-Side Request Forgery (SSRF) vulnerabilities leading to unauthorized sensitive data access or manipulation of internal systems

Medium

Unauthorized access to non-critical user data

Security misconfigurations that could be exploited under certain conditions

Limited Cross-Site-Scripting (XSS)

Malicious redirection without interaction on domains with already-connected wallet

Low

Minor information disclosure of sensitive data with low security risk

UI or UX bugs causing serious user confusion

Use of deprecated or outdated security practices that can cause security risk

Validation errors that lead to low-security risk

HTML and text injection in sensitive features with a low security risk

Other vulnerabilities with low-security impact

Blockchain

Critical

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

Transaction/consensus manipulation that leads to significant financial impact

Unauthorized token minting

Major

Transient consensus failures

Bad/incorrect usage of cryptography primitives

Consensus failures lead to compromising the integrity of the blockchain

Validator selection set manipulation

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

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.

Web Application

Best practice recommendations

Susceptibility to brute force attacks aimed at retrieving passwords or tokens

Non-Sensitive Data Disclosure

Attacks requiring physical access to a user's device

Exposure of non-sensitive API keys

Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions - Login/Logout CSRF

Reports exploiting the behavior of - or vulnerabilities in - outdated browsers

Unconfirmed reports from automated vulnerability scanners

Issues that require unlikely user interaction

Previously known vulnerable libraries without a working Proof of Concept

Missing best practices in SSL/TLS configuration

Any activity that could lead to the disruption of our service (DoS)

Email Spoofing - SPF/DMARC Records Misconfiguration

Spam / Flooding

Tab nabbing

Social engineering

Presence of autocomplete attribute on web forms

CORS misconfiguration with no security impact

Self-XSS with no security impact

CSV/formula injection

Missing HTTP security headers or cookie flags without demonstrated impact

Clickjacking with no security impact

Blockchain

Centralization risks

Best practice critiques

Impacts requiring basic economic and governance attacks (e.g. 51% attack)

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.

The following activities are prohibited by this bug bounty program:

Any testing with mainnet or public testnet contracts. All testing should be done on private testnets. 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 Scope9

Live SinceOct 14, 2025

Last Updated14d ago

Funds Reserved$1

Max Payout$0.13

Skynet Score

91.06

KYC

Not Required

PoC

Required

View on Skynet