CertiK LogoCertiK Logo
Bluefin logo
Bluefin
DeFi
DEX
Exchange
Max Payout
$5,000
Project Overview

Bluefin is a decentralized perpetuals trading protocol enabling users to trade perpetual contracts globally with leverage up to 20x. Designed for accessibility and flexibility, Bluefin provides a trustless platform for traders seeking high-leverage exposure within the decentralized finance ecosystem.

Rewards by Severity

Program Overview Bluefin is dedicated to maintaining a secure and resilient platform by encouraging the responsible disclosure of vulnerabilities through its Bug Bounty Program. This initiative invites ethical hackers and security researchers to contribute to the safety and integrity of Bluefin’s smart contracts, applications, and supporting infrastructure.

Reward Structure All reported vulnerabilities are assessed using a 4-tier severity model, with payouts determined based on both the criticality of the issue and the affected component. For critical smart contract vulnerabilities, rewards are capped at 10% of the economic damage, with consideration given to the amount of funds at risk, potential reputational damage, and other business impacts. High-severity vulnerabilities may be rewarded with up to 100% of the funds affected, based on the value calculated at the time of the report submission.

Submission Requirements Bug reports must include a Proof of Concept (PoC) along with clearly outlined steps to reproduce the issue. Reports that rely solely on narrative explanations or lack executable code will not be eligible for rewards.

Payouts Rewards are issued in USD and distributed directly by the Bluefin team.

Web Application
The bounty will be paid out in USD
Assets In-Scope
Target
Severity
Name
Web Application
Bluefin Swap
Web Application
Website
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.
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
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
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.
Web Application
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 - 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
Social engineering
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 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 SinceJun 16, 2025
Last Updated2mo 29d ago
Funds Reserved$15,000
Max Payout$5,000
Skynet Score
87.83
AA
KYC
Required
PoC
Required