People search HackerOne data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 HackerOne-linked incidents (1 company-confirmed), with headline counts up to 287 in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why HackerOne breach history matters
HackerOne operates in Technology (United States). Across indexed rows, recurring themes include credential theft and social engineering, third-party and supply-chain exposure. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — Klue OAuth supply-chain breach; Salesforce CRM business data accessed
Verified breach. HackerOne confirmed its Salesforce CRM was accessed as part of the Klue supply-chain attack on June 11–12, 2026. Threat actor Icarus used compromised legacy Klue credentials to steal OAuth tokens connecting Klue's market-intelligence platform to customer Salesforce instances. HackerOne's internal platform, vulnerability reports, and customer security program data were unaffected; only business contact/CRM records were accessed. HackerOne published a security update at hackerone.com/security-updates/klue-2026-06. Ic Exposed categories include Business contact information from HackerOne's Salesforce CRM: names, email addresses, job titles, phone numbers, and business addresses; no hacker vulnerability report data or cust. No attested victim count is published for this row yet. See the hackerone-klue-salesforce 2026 record and canonical BreachHistory entry.
2026 — 287 employees via Navia (BOLA; ~2.7M total Navia ecosystem)
Cataloged incident. Bug bounty platform HackerOne notified employees that personal data was exposed through U.S. benefits administrator Navia Benefit Solutions. Maine Attorney General filings and press reporting (March 2026) cited 287 affected individuals. Navia attributed unauthorized access to a Broken Object Level Authorization (BOLA) API issue with access between approximately December 22, 2025 and January 15, 2026; suspicious activity was identified January 23, 2026. Data types described included Social Security numbers, names, a Exposed categories include SSNs, names, addresses, phones, DOB, emails, benefit enrollment metadata. BreachHistory cites approximately 287 affected records in this row. See the hackerone 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Credential theft and social engineering — appears across multiple HackerOne catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple HackerOne catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Review OAuth app permissions and revoke unused third-party integrations.
- Step 5: Bookmark the HackerOne company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/hackerone · Latest: hackerone-klue-salesforce2026.
Sources: BreachHistory catalog (2 rows for HackerOne), company and regulator disclosures cited in individual breach records.