CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
WEMIX logo
WEMIX
Gaming
Play to Earn
Infrastructure
Max Payout
$20,000
Project Overview

WEMIX 3.0 is a decentralized blockchain protocol designed to deliver a seamless, user-centric experience. Powered by robust platform technology, it serves as the foundation for a borderless, cross-chain mega-ecosystem that integrates digital assets, applications, and services into a unified environment.

Rewards by Severity

Program Overview The WEMIX bug bounty program invites security researchers to responsibly disclose vulnerabilities affecting its smart contracts or application layers. The program is structured to reward meaningful contributions that improve the platform's robustness.

Reward Structure WEMIX uses a 4-tier severity model to assess submissions. Reward levels are determined by the severity of the issue and the type of system component affected (smart contract or frontend). High-impact vulnerabilities qualify for higher-tier payouts within a predefined structure.

Submission Requirements Each report must include a clear proof of concept (PoC) along with reproducible steps that demonstrate tangible impact on an in-scope asset. Code-based PoC is required; explanations or written descriptions alone will not be accepted.

Payouts Approved rewards are paid out according to internal team assessment, aligned with the severity model and submission quality.

Smart Contract
Blockchain
Application/Web
The bounty will be paid out in USD
Assets In-Scope
Target
Severity
Name
https://github.com/wemixarchive/go-wemix
Blockchain
WEMIX3.0 Public Blockchain
https://wemix.fi
Web Application
WEMIX DeFi Service
https://github.com/wemixarchive/wemix-lending-contract
Smart Contract
WEMIX DeFi Service
https://github.com/wemixarchive/governance-contract
Smart Contract
WEMIX3.0 Governance
https://github.com/wemixarchive/staking-contract
Smart Contract
Staking Contract
https://github.com/wemixarchive/weswap-periphery-contract
Smart Contract
WESWAP Periphery Contract
https://github.com/wemixarchive/weswap-core-contract
Smart Contract
WESWAP Core Contract
https://github.com/wemixarchive/stWemix-contract
Smart Contract
stWEMIX Contract
https://github.com/wemixarchive/wemixDollar-contract
Smart Contract
WEMIX Dollar Contract
https://github.com/wemixarchive/wwemix-contract
Smart Contract
WWEMIX Contract
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
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
Bad/incorrect usage of cryptography primitives
Transient consensus failures
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)
Application/Web
Critical
Achieving remote code execution on multiple hosts in the internal network
Gain core backend admin access; leak enterprise core data; and cause a severe impact
Unauthorized operation that involves money; payment logic bypassing
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
Leakage of a lot of source code
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
Medium impact information disclose
Low
General information leakage - such as web path traversal - system path traversal - directory browsing etc
Reflected XSS - DOM XSS and Flash-based XSS
SMS bombs - mail bombs (each system only accepts one type of this vulnerability)
No return value and no in-depth utilization of successful SSRF
Other vulnerabilities with low-security impact
CSRF 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)
Best practice critiques
Sybil attacks
Centralization risks
Blockchain
Centralization risks
Best practice critiques
Vulnerabilities that have already been exploited
Application/Web
Email Spoofing - SPF/DMARC Records Misconfiguration
Clickjacking
Any activity that could lead to the disruption of our service (DoS)
Missing best practices in SSL/TLS configuration
Previously known vulnerable libraries without a working Proof of Concept
Issues that require unlikely user interaction
Unconfirmed reports from automated vulnerability scanners
Reports exploiting the behavior of - or vulnerabilities in - outdated browsers
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions - Login/Logout CSRF
Non-Sensitive Data Disclosure - for example server version banners
CSV/formula injection
Self-XSS with no security impact
CORS misconfiguration with no security impact
Missing HttpOnly or Secure flags on cookies
Presence of autocomplete attribute on web forms
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 WEMIX services.
  • Do not attempt to perform brute-force attacks or denial-of-service attacks.
  • Do not attempt to target WEMIX 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 Scope10
Live SinceJul 31, 2023
Last Updated2mo 14d ago
Funds Reserved$100,000
Max Payout$20,000
Skynet Score
95.26
AAA
KYC
Required
PoC
Required
View on Skynet