CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
CROSS logo
CROSS
Web3
Gaming
Binance Alpha
Max Payout
$20,000
Project Overview

CROSS is a "Game Token Protocol" that leverages blockchain technology to transform this centralized structure, ensuring that players can fully enjoy the value they create themselves. It is “a protocol that allows every game to issue its own token”, and “a blockchain gaming platform” that facilitates free and transparent trading of assets by players. The vision of CROSS can be summarized in a single sentence: “To provide players with ownership of all in-game assets.

Rewards by Severity
Smart Contract
Blockchain
Application/Web
The bounty will be paid out in CROSS
Assets In-Scope
https://github.com/to-nexus/go-cross
Blockchain
CROSS Public Blockchain Mainnet
https://github.com/to-nexus/dex-contracts
Smart Contract
CROSS DEX Contract
https://github.com/to-nexus/token-forge-contracts
Smart Contract
CROSS Token Forge Contract
https://github.com/to-nexus/cross-ramp-token-preset-contracts
Smart Contract
CROSS Ramp Contract
https://github.com/to-nexus/bridge-contracts
Smart Contract
CROSS Bridge Contract
https://x.crosstoken.io/en/gametoken/CROSS/RUBYX
Web Application
CROSS Web - RUBYX
https://x.crosstoken.io/en/gametoken/CROSS
Web Application
CROSS Web - CROSS
https://x.crosstoken.io/en/gametoken/USDT
Web Application
CROSS Web - USDT
https://x.crosstoken.io/en/gametoken/VERSE8
Web Application
CROSS Web - VERSE8
https://x.crosstoken.io/rewards
Web Application
CROSS Rewards
https://x.crosstoken.io/en/bridge
Web Application
CROSS Bridge
https://wave.crosstoken.io/en
Web Application
CROSS Wave
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 project funds (other than unclaimed rewards)
Direct theft of user funds (other than unclaimed rewards)
Permanent freezing of funds
Unauthorized mint/burn/transfer of crypto assets
Bad randomness leading to predictable results with serious financial impact
Any governance voting result manipulation with serious impact
Protocol insolvency
Major
Temporary denial of services
Theft or permanent freezing of unclaimed yield
Broken access control leads to high security risks
Medium
Unexpected logic executions (doesn’t lose value)
Smart contract unable to operate due to lack of token funds or misconfiguration
Block stuffing for profit
Griefing (e.g. no profit motive for an attacker but damage to the users or the protocol)
Low
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
Blockchain
Critical
Network not being able to confirm new transactions (Total network shutdown)
Permanent freezing of funds (fix requires hard fork)
Transaction/consensus manipulation
Unauthorized token minting
Major
Transient consensus failures
Bad/incorrect usage of cryptography primitives
Validator selection set manipulation
Block synchronization failures
Medium
Vulnerability in RPC API (except via DDoS attack)
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)
Application/Web
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)
Cases where unintended errors cause direct damage to a user’s assets
Major
Sensitive user data disclosed for a large amount of users (i.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)
Public access to wallet information without connecting the wallet
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
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
Incorrect data supplied by third party oracles (Not to exclude oracle manipulation/flash loan attacks)
Basic economic governance attacks (e.g. 51% attack)
Not following best practices (with no security risk)
Issues with no security or financial impact
Best practice critiques
Sybil attacks
Centralization risks
Blockchain
Centralization risks
Best practice critiques
Vulnerabilities that have already been exploited
Application/Web
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(e.g. 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
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
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 CROSS services. Do not attempt to perform brute-force attacks or denial-of-service attacks. Do not attempt to target CROSS employees or its 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, 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 Scope12
Live SinceDec 6, 2025
Last Updated2d ago
Funds Reserved$100,000
Max Payout$20,000
Skynet Score
93.22
AAA
KYC
Required
PoC
Required
View on Skynet