CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
MARBLEX logo
MARBLEX
Gaming
NFT
Wallet
Max Payout
$1,000
Project Overview

MARBLEX, under the slogan “Fun Comes First,” uses blockchain technology to build a next-generation gaming and content ecosystem that prioritizes fun and immersion. MARBLEX delivers a fun and immersive Web3 entertainment experience to users by leveraging global success stories, expertise in virtual economy construction, and a diverse portfolio of game genres.

The MBX token serves as the main currency in the MARBLEX ecosystem and lets users engage with blockchain games and services integrated to MARBLEX. Through MARBLEX's Game, GameFi, and NFT services, users will gain access to a wide array of entertainment options and tangible value.

Rewards by Severity

Program Overview MARBLEX maintains a bug bounty program to safeguard the integrity of its blockchain-based gaming ecosystem. The program invites ethical hackers and security researchers to identify vulnerabilities in the MARBLEX smart contracts and related infrastructure, ensuring a secure environment for users and partners.

Reward Structure The program uses a 4-tier severity model to evaluate valid submissions, with reward amounts based on the criticality of the vulnerability and the type of asset impacted. For critical smart contract vulnerabilities, rewards are capped at 10% of the potential economic damage, with final considerations made by the MARBLEX team factoring in the value at risk, public relations, and brand exposure. High-severity smart contract vulnerabilities are further capped at up to 100% of the funds affected. All economic impact calculations are based on the blockchain state at the time the bug report is submitted.

Submission Requirements All submissions must include a working proof of concept (PoC) and detailed steps to reproduce the issue, clearly demonstrating the exploit’s impact on an in-scope asset. Submissions without executable code or that rely solely on written explanations will not qualify for rewards.

Payouts Rewards are denominated in USD and paid in USDT, distributed by the MARBLEX team after successful validation of the report and completion of the KYC process.

Smart Contract
Application/Web
The bounty will be paid out in USDT
Assets In-Scope
Target
Severity
Name
https://kaiascan.io/token/0xd068c52d81f4409b9502da926ace3301cc41f623?tabId=tokenTransfer&page=1
Smart Contract
MBX Token Contract
https://swap.marblex.io/en/swap
Web Application
MBX SWAP (DEX)
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
Major price manipulation (>=50)
Unauthorized mint/burn/transfer of assets
Major
Faulty usage of proxy patterns
Access control is bypassed - including privilege escalation
Medium
Unexpected logic executions (doesn’t lose value)
Weak random sources
Low
Smart contract functionality significantly differs from how it is described in its official repo
Missing events for functions that change critical parameters
Application/Web
Critical
Smart contract functionality significantly differs from how it is described in its official repo
Missing events for functions that change critical parameters
Major
Remote code execution and code 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
Reflected XSS - DOM XSS and Flash-based XSS
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
Best practice critiques
Centralization risks
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 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 SinceDec 20, 2023
Last Updated2mo 21d ago
Funds Reserved$10,000
Max Payout$1,000
Skynet Score
89.28
AA
KYC
Required
PoC
Required
View on Skynet