- Top reward
- $15,000
- Top severity paid
- Critical
- Assets in scope
- 16
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to $15,000
- for critical bugs.
- Report on HackerOne
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$15,000 from $6,001 |
| High |
|
$6,000 from $1 |
- Safe harbor
-
Full
Coinbase adheres to and supports the HackerOne Gold Standard Safe Harbor terms.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
16 assets you may test, 5 excluded.
Wildcard domains 5
- *.base.app Critical
- *.base.org Critical
- *.cbhq.net Critical
- *.coinbase.com Critical
- *.coinbase-corp.com Critical
Source code 4
- https://github.com/base/* Critical
- https://github.com/coinbase/* Critical
- https://github.com/coinbase/cb-mpc Critical
- https://github.com/coinbase/cb-mpc-go Critical No bounty
Android apps 2
- com.coinbase.android Critical
- org.toshi Critical
iOS apps 2
- com.vilcsak.bitcoin2 Critical
- org.toshi.distribution Critical
Networks 1
- 54.175.255.192/27 Critical
Products and areas 2
- https://chrome.google.com/webstore/detail/coinbase-wallet-extension/hnfanknocfeofbddgcijnmhnfnkdnaad Critical
- Other Medium No bounty
Out of scope (5)
- N/A - Not Coinbase owned or operated
- https://github.com/coinbase/x402
- https://github.com/x402-foundation/
- status.coinbase.com
- status.*.coinbase.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Coinbase (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Submit all valid, Coinbase-related bug reports through our programs on HackerOne (for Web2), and Cantina (for Web3).
-
Provide Coinbase a reasonable amount of time to fix a vulnerability prior to sharing details with any other party.
-
Adhere to HackerOne Disclosure Process.
-
Make a good faith effort to preserve the confidentiality and integrity of Coinbase customer data.
-
Do not defraud or attempt to defraud or socially engineer Coinbase customers or Coinbase itself.
-
Do not profit from vulnerabilities outside of Bug Bounty Program payouts.
-
Report vulnerabilities with no conditions, demands, or ransom threats.
Not accepted
-
Social engineering
-
Username enumeration
-
Rate Limiting (non-critical issues)
-
Physical security
-
Non-security-impacting UX issues
-
Deprecated open source libraries
-
Vulnerabilities in third-party applications that integrate with Coinbase
-
Ability to abuse existing banking functionality such as ACH or credit card chargebacks
-
Publicly available leaked credentials that have since been rotated
-
Demo apps, testnet, staging environments, etc.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, 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.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope removed
https://github.com/x402-foundation/ (out of scope)
-
Scope added
https://github.com/coinbase/x402 (out of scope)
-
Scope removed
tagomi.com (out of scope)
-
Scope removed
engineering.coinbase.com (out of scope)
-
Scope removed
international.coinbase.com
-
Scope removed
commerce.coinbase.com
-
Scope removed
pro.coinbase.com
-
Scope removed
api.coinbase.com
-
Scope removed
*.blockspring.com (out of scope)
-
Scope removed
api.custody.coinbase.com
-
Scope removed
paradex.io (out of scope)
-
Scope removed
com.coinbase.wallite
-
Scope removed
cloud.coinbase.com
-
Scope removed
com.coinbase.pro (out of scope)
-
Scope removed
blog.coinbase.com (out of scope)
-
Scope removed
Coinbase WaaS (Wallet as a Service)
-
Scope removed
institutional.coinbase.com
-
Scope removed
custody.coinbase.com
-
Scope removed
support.pro.coinbase.com (out of scope)
-
Scope removed
nft.coinbase.com
-
Scope removed
prime.coinbase.com
-
Scope added
https://github.com/coinbase/*
-
Scope removed
developers.coinbase.com (out of scope)
-
Scope removed
support.coinbase.com (out of scope)
-
Scope added
status.*.coinbase.com (out of scope)
-
Scope added
*.base.app
-
Scope added
https://github.com/base/*
-
Scope removed
Web3 Smart Contracts
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
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.
Coinbase's Bug Bounty Program exists to protect our two highest-priority assets: customer funds and customer information. We reward researchers who responsibly disclose software vulnerabilities that could put either at risk.
To be eligible for an award, a report must present a clear list of steps that when executed demonstrate the impact of a vulnerability that harms Coinbase or its customers. Coinbase determines eligibility and reward amounts at its sole discretion.
Scope
The scope of this program is Web2 products, assets and infrastructure owned by Coinbase. Please see the Scope page for more details. If you have a Web3 finding pertaining to Coinbase, please submit through our program on Cantina.
Out of scope
- Social engineering
- Username enumeration
- Rate Limiting (non-critical issues)
- Physical security
- Non-security-impacting UX issues
- Deprecated open source libraries
- Vulnerabilities in third-party applications that integrate with Coinbase
- Ability to abuse existing banking functionality such as ACH or credit card chargebacks
- Publicly available leaked credentials that have since been rotated
- Demo apps, testnet, staging environments, etc.
Severity & Rewards
Extreme — Up to $1,000,000
- Unauthorized access to Coinbase-owned hot/cold wallet assets, funds, or private keys.
Critical — Up to $15,000
- Market-moving API/service abuse.
- RCE on staking infrastructure.
- Easily-exploitable, high-severity bugs in protocols accessible from the public API (e.g., signing, DKG, TDH2 in the cb-mpc open-source library) that could lead to key compromise or RCE. Exploitation requires no material precondition beyond normal protocol operation, and broadly affects typical deployments.
- Large-scale money laundering.
- MNPI exposure, sustained business disruption, or significant monetary loss.
High — Up to $6,000
- PII exposure affecting a meaningful share of users.
- Fee-structure bypass at scale.
- KYC bypass.
- Single-product 2FA bypass.
- High-severity bugs in protocols accessible from the public API (e.g., signing, DKG, TDH2 in the cb-mpc open-source library) that could lead to key compromise or RCE, but require additional—yet realistic—conditions, access, or effort to exploit. Exploitation must remain feasible in a realistic deployment and must not depend on unlikely conditions.
Low / Medium — Out of Scope — $0
Severity is scored on impact (confidentiality, integrity, availability, fund and/or data exposure) and exploitability (access required, prerequisites, likelihood).
Note for the cb-mpc open-source library: the extreme category is out of scope, and hard to exploit bugs are considered medium, and therefore also out of scope.
Program Policies
Safe Harbor
- Coinbase adheres to and supports the HackerOne Gold Standard Safe Harbor terms.
Eligibility
- Not be a resident of any country under U.S. sanctions or any country that does not allow participation
- Be at least 14 years old with legal capacity to agree to these terms
- Have permission from your employer to participate
- Not be (for the previous 12 months) a Coinbase employee, immediate family member, contractor, or service provider
Researcher Requirements
- Submit all valid, Coinbase-related bug reports through our programs on HackerOne (for Web2), and Cantina (for Web3).
- Provide Coinbase a reasonable amount of time to fix a vulnerability prior to sharing details with any other party.
- Adhere to HackerOne Disclosure Process.
- Make a good faith effort to preserve the confidentiality and integrity of Coinbase customer data.
- Do not defraud or attempt to defraud or socially engineer Coinbase customers or Coinbase itself.
- Do not profit from vulnerabilities outside of Bug Bounty Program payouts.
- Report vulnerabilities with no conditions, demands, or ransom threats.
Violation of any of our policy may result in the immediate ban from further participation in the Coinbase Bug Bounty Program. Researchers who engage in extortion attempts will be reported to law enforcement.
Fine print
Coinbase may modify or cancel this program at any time. Anonymous HackerOne reports are accepted but not reward-eligible. This is v5.0 of the program; see also HackerOne's Finder Terms and Conditions.**