Skip to content

Crypto.com

Bug bounty on HackerOne crypto.com

Accepting reports
Top reward
$1,000,000
Top severity paid
Critical
Assets in scope
24
Public CVEs
2
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $1,000,000
for critical bugs.
Report on HackerOne
Submit through the program page.

Rewards

What HackerOne lists as the payout for each severity.

Severity Reward
Critical $1,000,000 from $200
High $10,000 from $5
Medium $2,000 from $3
Low $400 from $1

Scope

24 assets you may test, 7 excluded.

Web 16

  • app.mona.co Critical
  • developer-api.crypto.com Critical
  • developer.crypto.com Critical
  • developer-platform-api.crypto.com Critical
  • experiences.crypto.com Critical
  • https://crypto.com/exchange Critical
  • https://crypto.com/nft Critical
  • https://crypto.com/price Medium
  • js.crypto.com Critical
  • merchant.crypto.com Medium
  • nadex.com Medium
  • og.com Critical
  • tax.crypto.com Critical
  • tickets.crypto.com Critical
  • travel.crypto.com Critical
  • web.crypto.com Critical

APIs 2

  • Crypto.com Exchange APIs that require an account Critical
  • Crypto.com mobile app APIs that require an account Critical

Smart contracts 2

  • https://etherscan.io/token/0xfe18ae03741a5b84e39c295ac9c856ed7991c38e Critical
  • https://explorer.cronos.org/token/0x2e53c5586e12a99d4CAE366E9Fc5C14fE9c6495d Critical

Wildcard domains 2

  • *.crypto.com Critical
  • *.mona.co Critical

Android apps 1

  • co.mona.android High

iOS apps 1

  • com.monaco.mobile High
Out of scope (7)
  • com.defi.wallet
  • com.defi.wallet
  • Crypto.com Wallet Extension
  • https://github.com/crypto-com/chain-desktop-wallet
  • https://github.com/crypto-com/cro-staking
  • https://github.com/crypto-com/swap-contracts-core
  • https://github.com/crypto-com/swap-contracts-periphery

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Crypto.com (via HackerOne)'s policy. "We" in these lines means the program, not this site.

While testing

  • all reports must come with a valid Proof-of-Concept
  • We strictly prohibit any attacks targeting our users, employees, or staff.
  • You commit to not attempting to sabotage or disrupt any of our operations
  • You commit to following HackerOne's Code of Conduct
  • You commit to reporting potential security issues only through our Bug Bounty program
  • any report which included draining another individual's funds or blocking them access to their funds without their consent will automatically make you ineligible for this program

Not accepted

  • governance attacks
  • incorrect data supplied by third-party oracles
  • sybil attacks
  • lacks of liquidity
  • assets marked "Mock" or "Test"

Summarised with AI from the program policy on HackerOne, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2022-35936 High 8.2 5 Aug 2022
CVE-2021-43839 High 7.5 21 Dec 2021

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Our Products

As a globally regulated company, Crypto.com is required to follow various laws and regulations in order to provide you access to our services. This means that to gain access to our main product, the Crypto.com App, you will need to go through a Know-Your-Customer (KYC) signup flow. You can find more information at https://help.crypto.com/en/articles/6185958-how-to-sign-up-for-the-crypto-com-app. We encourage you to download our app at https://download.crypto.com!

Our app has over 100 million users and, as of December 2024, is the highest volume cryptocurrency trading app in the United States. While we understand that going through a sign-up process to gain access to our crown jewels is not ideal for ethical hackers, we are committed to making your experience with our program as quick, friendly, and fair as possible.

Please email us at [email protected] if you have any questions, comments, or need help related to our Bug Bounty program.

Thanks for reading and for considering hacking us!

Scope Message

We will accept reports on any asset that is within Crypto.com's control. For assets outside of our control, like vendors (e.g. https://help.crypto.com), we will accept reports if the vulnerability was caused due to a misconfiguration by us.

Out of Scope: User and Personnel Targeting

We strictly prohibit any attacks targeting our users, employees, or staff. This is out of scope and includes, but is not limited to:

  • Deceptive Software: Publishing or distributing malicious or baiting software, including IDE extensions (e.g., VSCode), browser extensions, AI skills, or public code packages.
  • Social Engineering: Attempting to trick or socially engineer staff or users into installing third-party tools or clicking links.
  • Unauthorized Data Collection: Extracting any data, beacons, or telemetry from our users' or staff members' machines, regardless of whether the data is deemed "harmless" or benign.
  • Malware: Any attacks involving viruses, trojans, or destructive payloads.

Commitments

By engaging in any activity under this HackerOne program:

  • We commit to working with you to making Crypto.com, our customers, and our products more secure
  • We commit to responding to all reports as soon as possible and in good-faith
  • We commit to honesty and transparency with you
  • We commit to evaluating all reports for bounty eligibility fairly and neutrally
  • We commit to making ourselves available upon request when reasonable to assist you
  • You commit to not engaging in any activities under this or any other Crypto.com-affiliated HackerOne programs as or with the assistance of a current or former employee, contractor, or vendor
  • You commit to not attempting to sabotage or disrupt any of our operations
  • You commit to following HackerOne's Code of Conduct
  • You commit to reporting potential security issues only through our Bug Bounty program

Smart Contracts

For vulnerabilities against in-scope smart contracts, please note that we score internally only based on potential impact to user funds and cryptographic security rather than CVSS 3.1. As always, all reports must come with a valid Proof-of-Concept. This means that reports operating on theoretical attacks such as governance attacks, incorrect data supplied by third-party oracles, sybil attacks, or lacks of liquidity are not considered valid reports.

We only consider the latest mainnet releases of blockchain assets as in-scope. We will not consider reports against assets marked "Mock" or "Test". Please note that any report which included draining another individual's funds or blocking them access to their funds without their consent will automatically make you ineligible for this program.

Extended Policy

This document is intended to be concise and precise. An extended version of our HackerOne policy, including sections such as Out-of-scope Vulnerabilities and Vulnerability Severity Definitions, can be found here.