People search HP data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 HP-linked incidents. This page maps every attested event through 2026 with internal links to canonical records.
Why HP breach history matters
HP operates in Technology (United States). Across indexed rows, recurring themes include mixed intrusion and disclosure events. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2018 — unauthorized access to customer names and email addresses
Cataloged incident. HP Inc. disclosed in late 2018 that unauthorized parties accessed an HP online store portal and obtained customer names and email addresses. The company stated payment card data was processed by third-party providers and not stored in the affected system. HP did not publish a large aggregate victim count in initial trade-press summaries; BreachHistory uses recordsAffected 0 pending regulatory filings. Exposed categories include Customer names and email addresses per HP notice. No attested victim count is published for this row yet. See the hp-customer-portal2018 and canonical BreachHistory entry.
2017 — MicTray keylogging to public MicTray.log (modzero disclosure)
Cataloged incident. Researchers at modzero disclosed that Conexant-signed audio helper components (`MicTray64.exe` / `MicTray.exe`) shipped on HP commercial laptops since late 2015 logged all keystrokes—often to `C:\Users\Public\MicTray.log`—under the guise of handling media hotkeys. PCMag and wider press treated it as negligent debug logging rather than targeted espionage, but the effect matched local keylogger behavior until HP/Conexant delivered updated driver packages. The issue is a canonical supply-chain software-quality case st Exposed categories include Local keystroke histories and thus any typed secrets while MicTray was active—no centralized breach headcount. No attested victim count is published for this row yet. See the hp2017 and canonical BreachHistory entry.
Patterns and analysis
- Mixed intrusion and disclosure events — appears across multiple HP 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 HP company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/hp · Latest: hp-customer-portal2018.
Sources: BreachHistory catalog (2 rows for HP), company and regulator disclosures cited in individual breach records.