OFZA Bug Bounty Program

OFZA is a VARA regulated cryptocurrency trading platform based in the UAE, designed to provide secure, seamless, and innovative crypto trading experiences for users across the UAE. With a focus on accessibility, security, and user-centric features, OFZA aims to bridge the gap between traditional finance and the world of digital assets.

Program Overview

The Ofza Bug Bounty Program is built to ensure the highest level of security for our user, partners, and infrastructure. As digital threats continue to evolve, we recognize the importance of working with the broader security community to stay ahead. The program empowers ethical hackers and security researchers to proactively report potential vulnerabilities, helping us to identify and fix issues before they can be exploited maliciously.

Rewards

OFZA provides rewards in USDT on Tron, denominated in USD.

Rewards by Threat Level

Websites and Applications

• Critical: Max $10,000 / Min $3,000
• High: Max $3,000 / Min $1,000
• Medium: Max $1,000 / Min $500

Critical Severity Criteria

For critical web/apps bug reports will be rewarded with USD $10,000 only if the impact leads to:

• A loss of funds involving an attack that does not require any user action
• Private key or private key generation leakage leading to unauthorized access to user funds

All other impacts that would be classified as Critical would be rewarded a flat amount of USD $3,000. The rest of the severity levels are paid out according to the Impact in Scope table.

Reward Payment Terms

Payouts are handled by the OFZA team directly and are denominated in USD. However, payments are done in USDT on Tron.

The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.

KYC Requirement

OFZA will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:

• Full name
• Date of birth
• Proof of address (either a redacted bank statement with address or a recent utility bill)
• Copy of Passport or other Government issued ID

Eligibility Criteria

Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:

• On OFAC's SDN list
• Official contributor, both past or present
• Employees and/or individuals closely associated with the project
• Security auditors that directly or indirectly participated in the audit review

Responsible Publication

OFZA adheres to Category 3 - Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports.

Primacy of Impact vs Primacy of Rules

OFZA adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.

Proof of Concept (PoC) Requirements

A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.

Public Disclosure of Known Issues

Bug reports covering previously-discovered bugs are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to "fix", necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk.

Known Issues:

• Email address enumeration

Previous Audits

OFZA's completed audit reports can be found at https://ofza.com. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.

Feasibility Limitations

The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.

Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.

Prohibited Activities

• Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
• Any testing with pricing oracles or third-party smart contracts
• Attempting phishing or other social engineering attacks against our employees and/or customers
• Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
• Any denial of service attacks that are executed against project assets
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty
• Any other actions prohibited by the Immunefi Rules