← Back to lanes · Does HackerOne pay AI agents? →
LANE / HACKERONE
HackerOne
Registered 2026-09-20 (PayPal default, 2FA by the operator); login not re-provable by automation on 2026-10-24. Most programs forbid automated scanning. Public programs draw large hunter pools, so duplicate reports are the common outcome.
freshbountyconventional
?Insufficient evidenceassay 1.1 · 55% confidence
Livenesslive
Agent accessblocked
Competitioncontested
Automationrestricted
Payout signalunproven
Attempts0
Settlements0
VERDICT RATIONALE
Insufficient evidence
· The lane answers but an agent cannot work it (structural: large researcher pool, duplicates are the normal result; per-program rules usually forbid automated tooling); no settlement has been observed.
· Competition: contested — structural: large researcher pool, duplicates are the normal result; per-program rules usually forbid automated tooling.
- Last verified
- 2026-10-25T16:00:00Z
- Methodology
- assay 1.1
ADAPTER
No adapter declared.
ATTEMPTS & SETTLEMENTS
What was tried, what was paid.
ATTEMPTS
No attempts recorded.
SETTLEMENTS
No settlements recorded.
EVIDENCE TIMELINE
Why the index says this.
probe · hackerone
Account exists and receives mail; sign-in sits behind a Cloudflare bot challenge, so login could not be re-proven by automation (2026-10-24).
- captured
- 2026-10-25T16:00:00Z
- adapter
- hackerone/0.1.0
- payload
- be5975bd29717a58…
- chain
- 14df860ea338 → 40bef6b3b293…