McKesson Data Breach History

This page tracks the McKesson data breach history and cybersecurity incidents affecting McKesson. BreachHistory currently indexes 2 publicly disclosed or catalogued incidents spanning 2014 through 2026, with approximately 11 thousand records reported as exposed across all indexed events. These totals may include overlapping datasets or third-party estimates and should not be interpreted as unique affected users.

The McKesson breach timeline includes major data breaches, cyber attacks, data leaks, credential exposures, API abuse, and other security incidents. Each incident provides details on the estimated records exposed, attack method, affected data types, and supporting public sources. Currently, 0 incidents are company-confirmed, while 1 remain unverified claims pending independent verification.

Largest McKesson Data Breaches

The largest indexed incidents include the 2014 McKesson (PST Services) — patient RCM data reachable via Google dorking; >10k…. Record counts originating from threat actors or leak sites should be treated as estimates unless confirmed by McKesson or a regulator. Below is the list of large data breaches:

• 2014 2014 McKesson (PST Services) — patient RCM data reachable via Google dorking; >10k individuals (Dec–Apr) — about 10.8K records exposed · Catalogued incident

What Information Was Exposed?

Depending on the incident, exposed data may include email addresses, Social Security numbers and national IDs, payment card and financial account data, health and medical (PHI) records, private messages and communications, and other personal information (PII). The exact data varies between incidents, so review each breach page before assuming your information was affected.

McKesson Data Breach 2026

At the time of this update, BreachHistory catalogues 1 2026 incident related to McKesson. Most recent entry: 2026 McKesson — ShinyHunters vishing/Salesforce-Snowflake claim; SEC 8-K confirms third-party app exfiltration. New incidents are added as official disclosures, regulatory filings, or credible cybersecurity reports become available.

What To Do If You Were Affected

If you believe your account may have been involved in a McKesson data breach, change any reused passwords, enable multi-factor authentication (MFA), monitor your account for suspicious activity, and be cautious of phishing emails or fake breach notifications.

This McKesson breach history is maintained by BreachHistory using public disclosures, regulatory filings, security research, and clearly labelled third-party claims. For the complete breach timeline, records exposed, incident details, and AI Breach Risk Score, explore the sections on this page.