People search Merck & Co. data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 Merck & Co.-linked incident, with headline counts up to 40K+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Merck & Co. breach history matters
Merck & Co. operates in Technology. Across indexed rows, recurring themes include third-party and supply-chain exposure, zero-day exploitation and malware. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2017 — NotPetya worm/crypto-wiper disrupted global IT and pharmaceutical manufacturing (Jun)
Cataloged incident. Merck became one of the largest NotPetya enterprise victims on June 27, 2017, as the worm moved from poisoned M.E.Doc update channels in Ukraine to multinational networks. Subsequent litigation exhibits summarized in SecurityWeek described ~10,000 endpoints infected within 90 seconds, ballooning past 40,000 worldwide, paralyzing email, manufacturing, and R&D systems—including Gardasil 9 fill-finish lines that drew FDA attention. Insurance Business recounts how Merck pursued ~$1.4 billion in traditional property cov Exposed categories include Primarily availability and operational data integrity loss; consumer HIPAA-style dossiers not the headline artifact of NotPetya. BreachHistory cites approximately 40K+ affected records in this row. See the merck-and-co2017 and canonical BreachHistory entry.
Patterns and analysis
- Third-party and supply-chain exposure — appears across multiple Merck & Co. catalog entries; prioritize controls that address this class of failure.
- Zero-day exploitation and malware — appears across multiple Merck & Co. 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 Merck & Co. company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/merck-and-co · Latest: merck-and-co2017.
Sources: BreachHistory catalog (1 row for Merck & Co.), company and regulator disclosures cited in individual breach records.