People search Chrome Web Store data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 Chrome Web Store-linked incident, with headline counts up to 37.4M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Chrome Web Store breach history matters
Chrome Web Store operates in Software (United States). Across indexed rows, recurring themes include 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 — 287 extensions, 37M installs, browsing data leak
Cataloged incident. Security researcher 'Q Continuum' identified 287 Chrome extensions (37.4M collective installs) leaking browsing history to external parties. Exfiltrated: URLs, search queries, referrers, timestamps, cookies. Recipients included Similarweb, Semrush, Big Star Labs, unknown/Chinese actors. Extensions used encryption/obfuscation. Categories: VPNs, productivity, PDF, shopping. Notable: Pop-up Blocker, Stylish, SimilarWeb, WOT, Video Ad Blocker Plus. Exposed categories include Browsing URLs, search queries, referrers, timestamps, cookies. BreachHistory cites approximately 37.4M+ affected records in this row. See the chrome-extensions 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Third-party and supply-chain exposure — appears across multiple Chrome Web Store 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: Bookmark the Chrome Web Store company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/chrome-web-store · Latest: chrome-extensions2026.
Sources: BreachHistory catalog (1 row for Chrome Web Store), company and regulator disclosures cited in individual breach records.