CertiK LogoCertiK Logo
IceCreamSwap logo
IceCreamSwap
DEX
DeFi
Lending & Borrowing
Max Payout
$5,000
Project Overview

IceCreamSwap is a multi-chain DeFi ecosystem offering a suite of tools including a DEX, DEX-aggregator, cross-chain bridge, launchpad, KYC system, and staking pools. Designed to guarantee users the best trading prices, IceCreamSwap supports a wide range of networks such as Binance Smart Chain (BSC), CORE DAO, XDC, Telos, Bitgert, and more—making it a one-stop platform for seamless DeFi access across chains.

Rewards by Severity

Program Overview The IceCreamSwap Bug Bounty Program invites security researchers and ethical hackers to identify and report vulnerabilities within the IceCreamSwap ecosystem. This initiative strengthens the platform’s reliability, protects user funds, and ensures the secure operation of its smart contract infrastructure.

Reward Structure All valid reports are evaluated using a 4-level severity model, with payouts based on the severity and scope 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 as well as potential PR and brand implications, as determined by the IceCreamSwap team. High-severity vulnerabilities are eligible for rewards up to 25% of the funds affected, calculated at the time the report is submitted.

Submission Requirements Submissions must include a working proof of concept (PoC) and detailed reproduction steps. Reports that do not contain code or fail to demonstrate a tangible impact on an in-scope asset will be disqualified.

Payouts All rewards are denominated and paid in ICE, and are distributed directly by the IceCreamSwap team following successful validation and completion of KYC.

Smart Contract
Application/Web
The bounty will be paid out in ICE
Assets In-Scope
Target
Severity
Name
Web Application
IceCreamSwap.com UI
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
Unauthorized mint/burn/transfer of assets
Permanent denial of services
Double spending
Protocol insolvency
Major
Access control is bypassed - including privilege escalation
Theft or permanent freezing of unclaimed yield
Medium
Unexpected logic executions (doesn’t lose value)
Griefing (e.g. no profit motive for an attacker but damage to the users or the protocol)
Low
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
Application/Web
Critical
Theft of users funds
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
Medium
Account takeover
Stored XSS on general pages
CSRF involving core business etc
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
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
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:
  • 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 SinceSep 1, 2023
Last Updated4mo 28d ago
Funds Reserved$20,000
Max Payout$5,000
Skynet Score
78.57
BBB
KYC
Required
PoC
Required