Bug bounty program
Scopely
- Platform
- HackerOne
- Bounties
- Pays
- Assets in scope
- 24
- Disclosed reports
- 0
- Subdomains
- 3,670
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains3,670
| Name | Scope | First seen |
|---|---|---|
| jenkins.luna-dev.scopely.comci, dev | In scope | 2026-11-14 |
| teamcity.poe-dev.scopely.comci, dev | In scope | 2026-11-14 |
| jenkins-np.luna-dev.scopely.comci, dev | In scope | 2026-11-14 |
| jenkins-cdk.luna-dev.scopely.comci, dev | In scope | 2026-11-14 |
| teamcity-hooks.poe-dev.scopely.comci, dev | In scope | 2026-11-14 |
| teamcity-redirect.poe-dev.scopely.comci, dev | In scope | 2026-11-14 |
| teamcity-artifacts.poe-dev.scopely.comci, dev | In scope | 2026-11-14 |
| argocd.ssvcs1-euw1.internal.shared-services.electrum.scopely.comci, internal | In scope | 2026-11-14 |
3,667 names are covered by the program's own scope; 6 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.
A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-15.