Skip to content

Fireblocks Web Managed Bug Bounty Engagement

By Fireblocks Bug bounty on Bugcrowd fireblocks.io

Accepting reports Full safe harbor
Top reward
$12,000
Top severity paid
Critical
Assets in scope
3
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $12,000
for critical bugs, from $20.
Full safe harbor
Good-faith research is authorised; no legal action.
No public write-ups
Keep findings private.

Rewards

What Bugcrowd lists as the payout for each severity.

Severity Reward
Critical $12,000 from $7,000
High $9,000 from $1,000
Medium $1,500 from $300
Low $300 from $20
Safe harbor
Full Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy;

Summarised with AI from the program policy on Bugcrowd, read 12 Nov 2026, and checked word for word against it. Read the original

Earlier reward tables (1)
  • 11 Nov 2026 to 11 Nov 2026: Critical up to $12,000

Scope

3 assets you may test.

Web 3

  • https://sandbox-api.fireblocks.io
  • https://sb-console-api.fireblocks.io
  • https://sb-mobile-api.fireblocks.io

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Fireblocks Web Managed Bug Bounty Engagement (via Bugcrowd)'s policy.

While testing

  • To gain access to the application, please sign up for an account using your @bugcrowdninja.com email address.
  • If you believe you've identified a vulnerability that may lead to post-exploitation activity including modification or destruction of data please stop testing and submit your finding.

Not accepted

  • P5 vulnerabilities
  • DoS/DDoS/Network DoS
  • Rate limiting bypass attempts
  • Email bombing flooding
  • Social engineering attacks
  • Phishing attacks
  • Physical attacks

Summarised with AI from the program policy on Bugcrowd, 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.

Public CVEs

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

Search 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 bugcrowd.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Description

Fireblocks is an enterprise-grade platform delivering a secure infrastructure for moving, storing, and issuing digital assets. Fireblocks enables exchanges, custodians, banks, trading desks, and hedge funds to securely scale digital asset operations through patent-pending SGX & MPC technology. Thank you for helping keep Fireblocks and our users safe! Ratings/Rewards For the initial prioritization/rating of findings, this engagement will use the Bugcrowd Vulnerability Rating Taxonomy . However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority.

Targets

Testing is only authorized on the targets listed as in scope. Any domain/property of Fireblocks not listed in the targets section is out of scope. This includes any/all subdomains not listed above. If you happen to identify a security vulnerability on a target that is not in scope, but it demonstrably belongs to Fireblocks, you can report it to this engagement. However, be aware that it is ineligible for rewards or points-based compensation. Focus Areas Performing unauthorized actions with an emphasis on unauthorized funds transfer Disclosure of sensitive or personally identifiable information Cross-Site Scripting (XSS) Cross-Site Request Forgery (CSRF) for sensitive functions in a privileged context Server-side or remote code execution (RCE) Authentication or authorization flaws, including insecure direct object references and authentication bypass Injection vulnerabilities, including SQL and XML injection Directory traversal Significant security misconfiguration with a verifiable vulnerability Credentials To gain access to the application, please sign up for an account using your @bugcrowdninja.com email address. The registration will not work with an email other than @bugcrowdninja.com. For more info regarding @bugcrowdninja email addresses, see here . You may register for accounts here . Excluded Submission Types P5 vulnerabilities Availability/volumetric testing e.g.: DoS/DDoS/Network DoS Rate limiting bypass attempts Email bombing flooding N-day/Third party 0-day Policy When N-Day bugs are released to the public, we will consider these as in scope after 14 days has gone by e.g: N-day released on 01/01/2025, we would consider it in-scope on 01/15/2025 Out of Scope Interacting or manipulate other stakeholders and their associated accounts including: Social engineering attacks Phishing attacks Physical attacks Third party providers and services Potential post-exploitation scenarios : If you believe you've identified a vulnerability that may lead to post-exploitation activity including modification or destruction of data please stop testing and submit your finding. We will work with you to evaluate the vulnerability and award you accordingly for the final impact and severity. Stolen/Breached Credentials If you happen to identify vulnerabilities involving data that has been exposed or leaked such as dark web forums or leaked credential sites, you can report it to this engagement. However, be aware that it is only eligible for points-based compensation. This policy helps maintain the highest standard of operational confidentiality, integrity, and compliance. Safe Harbor When conducting vulnerability research according to this policy, we consider this research to be: Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy; Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls; Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; and Lawful, helpful to the overall security of the Internet, and conducted in good faith. You are expected, as always, to comply with all applicable laws. If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please inquire through the Bugcrowd Support Portal before going any further.

In scope (in scope)

Get Started To gain access to the application, please sign up for an account using your @bugcrowdninja.com email address. The registration will not work with an email other than @bugcrowdninja.com. For more info regarding @bugcrowdninja email addresses, see here . You may register for accounts here . Target Information: With the objective of securing the most widely used protocols and signature schemes, this program focuses on the highest priority signature scheme, the MPC protocol for ECDSA signatures used in Bitcoin, Ethereum, and other blockchains, as well as the protocol for EdDSA. You can find further documentation here: https://developers.fireblocks.com/docs/sandbox-quickstart https://developers.fireblocks.com/docs/postman-guide