CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
MoonCat AI logo
MoonCat AI
DeFi
Yield Farming
Memes
Max Payout
$1,000
Project Overview

MoonCat.ai (MCT) is a DeFi protocol on the UniChain network, combining secure tokenomics with advanced staking technology. With a fixed supply of 1 billion MCT, its transparent allocation includes 40% for public sale, 50% for liquidity and cross-chain bridges, and 10% for development and marketing.

Rewards by Severity

Program Overview The MoonCat Production Systems Bug Bounty Program is designed to identify and address verified vulnerabilities within the live production environment. By encouraging responsible disclosure from ethical hackers and security researchers, MoonCat aims to enhance the resilience, security, and integrity of its deployed systems.

Reward Structure All valid submissions are evaluated using a standardized 4-tier severity model, with reward amounts determined based on severity, reproducibility, and impact. Eligible vulnerabilities may receive up to $1,000, depending on the classification level. Final reward determinations are made by the MoonCat security team.

Submission Requirements To qualify for a reward, all bug reports must include a working proof of concept (PoC) and step-by-step reproduction instructions. The vulnerability must demonstrate a real-world impact on an in-scope live production asset. Submissions lacking executable code or affecting non-production environments will not be considered.

Payouts Bounties are denominated and paid in USDT, processed directly by the MoonCat team upon successful report validation and KYC compliance.

Smart Contract
Web Application
The bounty will be paid out in USDT
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
Protocol insolvency
Major
Theft or permanent freezing of unclaimed yield and rewards
Temporary denial of services
Broken access control leads to high security risks
Medium
Smart contract unable to operate due to lack of funds or misconfiguration
Griefing attacks that can damage users or the protocol without profiting the attacker
Block stuffing for profit
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)
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
Basic economic governance attacks (e.g. 51% attack)
Not following best practices with no security risk
Sybil attacks
Issues with no security or financial impact
Web Application
Best practice recommendations
Non-Sensitive Data Disclosure
Exposure of non-sensitive API keys
Unconfirmed reports from automated vulnerability scanners
Missing best practices in SSL/TLS configuration
Self-XSS with no security impact
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 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 Scope4
Live SinceJun 8, 2025
Last Updated4mo 28d ago
Funds Reserved$10,000
Max Payout$1,000
Skynet Score
86.58
AA
KYC
Required
PoC
Required
View on Skynet