Decentralized Security, Community-Powered Recon

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

CYBRO

Asset Management

DeFi

Lending & Borrowing

Max Payout

$10,000

Project Overview

CYBRO is a multichain earn marketplace providing secure and seamless access to leading Web3 investment opportunities. Featuring AI-powered portfolio management, an intuitive user interface, and responsive customer support, CYBRO simplifies decentralized investing while maximizing returns across multiple blockchain ecosystems.

Rewards by Severity

Program Overview The CYBRO Bug Bounty Program is established to proactively identify and resolve security vulnerabilities within the CYBRO ecosystem. By inviting ethical hackers and developers to participate, CYBRO reinforces its commitment to maintaining a secure and trustworthy platform.

Reward Structure All submitted reports are assessed using a standardized 4-tier severity model, with rewards based on the criticality and impact of the issue. For critical smart contract vulnerabilities, rewards are capped at 10% of the economic damage, factoring in the amount of funds at risk, along with public relations and brand considerations at the discretion of the CYBRO team. High-severity vulnerabilities are eligible for up to 100% of the funds affected, based on conditions at the time of submission.

Submission Requirements Bug reports must include a working proof of concept (PoC) and detailed steps to reproduce the vulnerability. Only submissions that clearly demonstrate an end-effect on an asset-in-scope will be considered. Reports consisting solely of theoretical analysis or lacking code will be rejected.

Payouts All bounty rewards are denominated and paid in USDT, and distributed by the CYBRO team after successful report verification.

Smart Contract

Web Application

Blockchain

The bounty will be paid out in USDT

Assets In-Scope

Target

Severity

Name

https://github.com/cybro-io

Smart Contract

Pre-Sale and Token contracts

http://cybro.io

Web Application

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.

Smart Contract

Critical

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

Freezing or shutdown of systems

Major price manipulation (>=50)

Unauthorized mint/burn/transfer of assets

Permanent denial of services

Double spending

Protocol insolvency

Major

Faulty usage of proxy patterns

Minor price manipulation

Temporary denial of services

Temporary freezing of funds for any amount of time

Access control is bypassed - including privilege escalation

Theft or permanent freezing of unclaimed yield

Medium

Unexpected logic executions (doesn’t lose value)

Users could lose funds due to rounding

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

Weak random sources

Low

Non-intuitive return values

Important gas optimizations

Smart contract functionality significantly differs from how it is described in its official repo

Smart contract fails to deliver promised returns - but doesn’t lose value

Missing events for functions that change critical parameters

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)

Major

Remote code execution and code injection

SQL injection

Obtaining high-impact sensitive information from the internal system

XXE/XML injection vulnerability with high-security impact

Authentication and authorization bypass with high impact

Wormable stored XSS

Large scale account takeover

Medium

Account takeover

Stored XSS on general pages

CSRF involving core business

IDOR with medium security impact/Horizontal and Vertical Privilege Escalation

The leakage of locally-stored sensitive authentication key information

Low

General information leakage - such as web path traversal - system path traversal - directory browsing etc

Reflected XSS - DOM XSS and Flash-based XSS

Blockchain

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

Unauthorized token minting

Major

Unintended chain split (fix not requiring hard fork)

Transient consensus failures

Bad/incorrect usage of cryptography primitives

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

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.

Smart Contract

Best practice critiques

Web Application

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

Blockchain

Best practice critiques

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 Scope2

Live SinceApr 11, 2024

Last Updated3mo 22d ago

Funds Reserved$25,000

Max Payout$10,000

Skynet Score

81.35

KYC

Not Required

PoC

Required

View on Skynet