People search 1Password data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 1Password-linked incidents. This page maps every attested event through 2026 with internal links to canonical records.
Why 1Password breach history matters
1Password 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
2024 — CVE-2024-42219 macOS XPC flaw, local vault exfiltration
Cataloged incident. Insufficient XPC validation in 1Password 8 for Mac (versions before 8.10.36). Local malware could bypass platform security to hijack browser extension/CLI and exfiltrate vault items, account unlock key, SRP-x. Robinhood Red Team disclosed; patched in 8.10.36. No evidence of in-the-wild exploitation. Exposed categories include Potential: vault items; account unlock key; SRP-x (if malware present). No attested victim count is published for this row yet. See the 1password2024 and canonical BreachHistory entry.
2023 — Okta support breach, session compromise
Cataloged incident. Threat actor used stolen session cookie from HAR file uploaded to Okta support. Accessed 1Password Okta instance; attempted IdP update, admin report. No user data accessed; vaults encrypted. Sessions cleared, creds rotated. Exposed categories include None; no user data; admin reconnaissance only. No attested victim count is published for this row yet. See the 1password2023 and canonical BreachHistory entry.
Patterns and analysis
- Credential theft and social engineering — appears across multiple 1Password catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple 1Password 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 1Password company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/1password · Latest: 1password2024.
Sources: BreachHistory catalog (2 rows for 1Password), company and regulator disclosures cited in individual breach records.