CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
ONFA logo
ONFA
DEX
Mining Pool
NFT
Max Payout
$50,000
Project Overview

Overview of Onfa Fintech

Onfa Fintech is committed to delivering the highest levels of transparency and trust in the blockchain space, with a focus on enhancing the standards of safety and security for digital financial systems. Our mission is to empower customers and partners with confidence in the blockchain solutions we develop.

By leveraging cutting-edge technology and innovative approaches, Onfa Fintech consistently builds a robust foundation to protect user assets and data while optimizing security in blockchain applications. To learn more about Onfa Fintech’s products and services, please visit our official website https://onfa.io.

Bug Bounty Program and Requirements

Rewards Based on Severity

To maintain the highest standards of system quality and security, Onfa Fintech encourages security professionals and bug hunters to report vulnerabilities. The program’s conditions and rewards are outlined as follows: 1. Bug Report Requirements: • Reports must include: • Proof of Concept (PoC). • Detailed steps to reproduce the vulnerability, along with its final impact on the assets in scope. • Reports that only contain explanations or descriptions without accompanying PoC code will not be accepted. 2. Reward Limits: • Critical smart contract vulnerabilities: • Maximum reward: 10% of the economic damage caused, with additional considerations such as brand and public relations impact. • High-severity smart contract vulnerabilities: • Maximum reward: 100% of the affected amount. • All calculations regarding the at-risk amount will be based on the time the bug report is submitted.

KYC (Know Your Customer) Requirements

To ensure transparency and compliance, bug hunters seeking rewards must complete KYC verification, which includes: • Identity verification with valid identification documents. • Proof of residency documentation.

Ineligible Conditions

• Bug reports that duplicate previously discovered vulnerabilities will not be eligible for rewards. • If a report includes known issues, it will be rejected along with evidence that the issue had been documented prior to submission.

Onfa Fintech welcomes contributions from the community to enhance system security and transparency. Let’s work together to build a safer and more reliable blockchain future!

Rewards by Severity
Web Application
The bounty will be paid out in USDT
Assets In-Scope
Target
Severity
Name
https://apps.apple.com/us/app/onfa-wallet/id6503425909
Mobile Application
Mobile Wallet Application
https://play.google.com/store/apps/details?id=com.onfanapp.id869194869194
Mobile Application
Mobile Wallet Application
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)
Major
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
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
Use of deprecated or outdated security practices that can cause security risk
Validation errors that lead to low-security risk
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
Previously known vulnerable libraries without a working Proof of Concept
Any activity that could lead to the disruption of our service (DoS)
Email Spoofing - SPF/DMARC Records Misconfiguration
Spam / Flooding
CORS misconfiguration with no security impact
Self-XSS with no security impact
Missing HTTP security headers or cookie flags without demonstrated 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:
  • 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 SinceNov 20, 2024
Last Updated9mo 26d ago
Funds Reserved$500,000
Max Payout$50,000
Skynet Score
90.08
AA
KYC
Required
PoC
Required
View on Skynet