People search Huntress data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 Huntress-linked incident (1 company-confirmed). This page maps every attested event through 2026 with internal links to canonical records.
Why Huntress breach history matters
Huntress operates in Technology (United States). Across indexed rows, recurring themes include third-party and supply-chain exposure, unverified actor or scraping claims. 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 & Gong CRM data exfiltrated
Verified breach. Downstream Klue supply-chain victim — June 2026. Huntress publicly disclosed that the Icarus extortion group's compromise of Klue (see klue-oauth-supply-chain2026) enabled exfiltration from Huntress's Salesforce and Gong environments via stolen Klue integration OAuth tokens. Huntress confirmed copied data included business contacts (names, work emails, titles, phones, business addresses), pricing/quotes, sales messaging, and opportunity notes—not threat intelligence, customer/partner credentials, payment data, or H Exposed categories include Business contacts, price quotes, sales communications, opportunity notes, subscription/pricing details, competitive market reports per Huntress—no threat intel, customer credential. No attested victim count is published for this row yet. See the huntress-klue-salesforce 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Third-party and supply-chain exposure — appears across multiple Huntress catalog entries; prioritize controls that address this class of failure.
- Unverified actor or scraping claims — appears across multiple Huntress 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 Huntress company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/huntress · Latest: huntress-klue-salesforce2026.
Sources: BreachHistory catalog (1 row for Huntress), company and regulator disclosures cited in individual breach records.