Skip to content
Sign in

Bug bounty program

HA

HackerOne

Open on HackerOneAtlas
Platform
HackerOne
Bounties
Pays
Assets in scope
26
Disclosed reports
607
Subdomains
127
Vendor on CyberSIXT
HackerOne (470 CVEs, 0 exploited)

Most upvoted reports607

All reports
Most upvoted reports of HackerOne
ReportWeaknessDisclosedBountyVotes
Account takeover via leaked session cookieAnalysed#745324Authentication2019-12-03$20,0001,642
Confidential data of users and limited metadata of programs and reports accessible via GraphQLAnalysed#489146Information Disclosure2019-02-03–1,033
WannaCrypt “Killswitch”Analysed#228648No weakness recorded2017-05-13–809
Email address of any user can be queried on Report Invitation GraphQL type when username is knownAnalysed#792927Access Control2020-02-20–671
The /reports/:id.json endpoint discloses potentially sensitive user attributes when reporter summary is presentAnalysed#3000510Information Disclosure2025-04-01–625
Customer private program can disclose email any users through invited via usernameAnalysed#807448Information Disclosure2020-05-15$7,500589
Server Side Request Forgery (SSRF) via Analytics ReportsAnalysed#2262382Server-Side Request Forgery2023-12-08$25,000529
profile-picture name parameter with large value lead to DoS for other users and programs on the platformAnalysed#764434Denial of Service2020-03-25–475
How the Bug stole hackingAnalysed#762510Insecure Direct Object Reference2019-12-20–471
An attacker can can view any hacker email via /SaveCollaboratorsMutation operation nameAnalysed#2032716Information Disclosure2023-07-04$12,500429

Subdomains127

Root:hackerone.com
Scope
Name suggests
First seen
Text fileClear filters26 names
Subdomains of HackerOne
NameScopeFirst seen
3d.hackerone.comNot in the scope2026-11-14
url824.advocacy.hackerone.comNot in the scope2026-11-14
api.hackerone.comapiIn scope2026-11-14
apis.hackerone.comapiNot in the scope2026-11-14
mta-sts.ave-mail.hackerone.commailNot in the scope2026-11-14
design.hackerone.comNot in the scope2026-11-14
docs.hackerone.comNot in the scope2026-11-14
email.hackerone.comNot in the scope2026-11-14
o1.email.hackerone.comNot in the scope2026-11-14
o2.email.hackerone.comNot in the scope2026-11-14
o3.email.hackerone.comNot in the scope2026-11-14
events.hackerone.comNot in the scope2026-11-14
mta-sts.forwarding.hackerone.comNot in the scope2026-11-14
go.hackerone.comNot in the scope2026-11-14
gslink.hackerone.comNot in the scope2026-11-14
info.hackerone.comNot in the scope2026-11-14
links.hackerone.comNot in the scope2026-11-14
managed.hackerone.comNot in the scope2026-11-14
mta-sts.managed.hackerone.comNot in the scope2026-11-14
mta-sts.hackerone.comNot in the scope2026-11-14
ns.hackerone.comNot in the scope2026-11-14
a.ns.hackerone.comNot in the scope2026-11-14
b.ns.hackerone.comNot in the scope2026-11-14
resources.hackerone.comNot in the scope2026-11-14
support.hackerone.comListed out of scope2026-11-14
www.hackerone.comIn scope2026-11-14

24 names are covered by the program's own scope; 0 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-14.

CyberSIXTSignal over noise
Updated AboutDevelopersSign in