Skip to content

BlazePhoenix

Vulnerability disclosure program on Self-hosted blazephoenix.xyz

Accepting reports Full safe harbor
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
16
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 3 days
As the policy promises.
No public write-ups
Keep findings private.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Pays cash
No Rewards are paid in BZPX , not stablecoins or ETH.
Response
Within 3 days We acknowledge within 72 hours and keep you updated through triage and the fix.
Hall of fame
Yes Valid, previously-unknown findings are credited by the name or handle you choose, with your consent, whether or not an award applies.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

16 assets you may test, 5 excluded.

Source code 4

  • BlazePhoenixStaking, BlazePhoenixMathLib
  • https://github.com/blazephoenixxyz-crypto/Blaze-Phoenix-Dex/blob/main/llms.txt
  • https://github.com/security/advanced-security
  • Router, Solver, Hub, Quoter, Gate and GateWrapper, the Core and Math libraries and the BalancerV2, BalancerV3, CurveNG and CurveCryptoNG adapters — the 2.0.0 release

APIs 2

  • /api/quote, /api/verify, /api/stats, /api/tape, /api/openapi and the rest of blazephoenix.xyz/api
  • Public API (blazephoenix.xyz/api)

Domains 2

  • blazephoenix.xyz
  • blazephoenix.xyz — the swap, staking and api tabs

Web 2

  • blazephoenix.xyz/mcp, /.well-known/mcp.json, /agents, llms.txt and the machine-readable files
  • Website (blazephoenix.xyz swap, staking and API tabs)

Products and areas 6

  • MCP server and agent surfaces (blazephoenix.xyz/mcp, @blazephoenix/mcp)
  • other
  • SDK and calldata (@blazephoenix/sdk)
  • Solidity contracts of the DEX aggregator (Router, Solver, Hub, Quoter, Core)
  • Solidity contracts of the staking engine (BlazePhoenixStaking, BlazePhoenixMathLib)
  • the route and calldata our API, MCP and front end hand to integrators
Out of scope (5)
  • RPC providers and front-ends
  • the BZPX token itself is out of scope
  • The earlier 1.0.0 deployment, which the 2.0.0 release replaces.
  • Theoretical concerns without demonstrated impact
  • Third-party code: pools, tokens, bridges, wallets, RPC providers, Cloudflare, GitHub — unless our code consumes them unsafely.

Rules

What the policy asks of you, and the bug types it won't reward, quoted from BlazePhoenix's policy.

While testing

  • Test on a fork — every contract is deterministic and forkable.
  • Email your proof of concept to [email protected] — never a public issue.
  • Include the impact, the affected contract or endpoint and file:line where possible, a runnable proof of concept (a Foundry test on a fork, or an exact request sequence), and your own severity and likelihood.
  • Please reference GitHub file paths and commits in your submissions.
  • Disqualifies a report: testing against other users' funds on mainnet, or disclosing before a fix.

Not accepted

  • Missing headers or cookie flags, SPF/DKIM/DMARC, clickjacking, CSRF, and CORS on public read-only endpoints — without demonstrated impact.
  • Self-XSS, tab-nabbing, open redirects and text injection without impact.
  • Outdated dependencies or versions without a working exploit.
  • Gas optimisations, style, best-practice and informational notes.
  • Theoretical reports without a proof of concept, and unverified AI-generated reports.
  • Display glitches (stale figures, layout) that cannot change what a user signs.
  • Social engineering, phishing and physical attacks.
  • Volumetric DoS, load testing, spam, and rate-limit exhaustion of the free public API.
  • Price movement, MEV and front-running that settle at or above the minimum the user signed.
  • Attacks that need a compromised private key, admin key, or the victim’s own device.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 5 hours 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.