McKesson Data Breach: What Happened and What You Should Do
McKesson disclosed a data breach affecting an unconfirmed number of people. Here's what is currently known about the incident, what information may have been exposed, and steps you can consider taking.
- Company
- McKesson
- People affected
- Unconfirmed
McKesson's Sept. 8, 2026 substitute notice does not state how many people are affected. On Sept. 10, 2026, The Register reported Have I Been Pwned added leaked McKesson data covering roughly 6.4 million individuals. ShinyHunters previously claimed about 284 million data records (not unique people). This page does not treat either third-party figure as a company confirmation.
- Incident date
- August 20 – August 25, 2026
- Discovered
- August 25, 2026
- Disclosed
- August 28, 2026
- Information exposed
- Possibly: Name, Physical address, Phone number, Email address, Date of birth, Account information, Insurance information, Health information, Financial information, Social Security number, Government identification
- Status
- Under investigation
McKesson says its data review is early-stage, it contained the incident, engaged external cybersecurity experts, notified law enforcement, added safeguards, and continues monitoring. Individual notification will follow work with customers after the review. Substitute notice posted September 8, 2026.
What happened in the McKesson breach?
How the attacker got in
Unauthorized access involving employee corporate accounts and third-party applications, with data exfiltration, per McKesson's Sept. 8 notice. McKesson has not publicly confirmed the initial access method. News outlets have attributed the intrusion to the ShinyHunters extortion group (including claimed vishing against employees); McKesson has not confirmed that attribution in the substitute notice.
Reports conflict
Timeline of what is known
- 01August 20 – August 25, 2026Unauthorized access
- 02August 25, 2026Breach discovered
- 03August 28, 2026Breach disclosed publicly
- 04September 8, 2026Affected individuals notified
Dates come from the sources listed at the bottom of this page. Separate events are kept separate; where a date has not been disclosed, it says so.
What information was exposed?
The categories below come from McKesson's disclosure and the sources listed on this page. Each is labeled by what the evidence supports. Categories not mentioned in any source are not listed, even if they are common in similar breaches.
Name
First and last name, per McKesson's Sept. 8 substitute notice.
Physical address
Phone number
Email address
Date of birth
Account information
Patient IDs and related identifiers, per the notice.
Insurance information
Health plan / policy details, member/group IDs, Medicaid-Medicare-government payor IDs.
Health information
Dates of service, medical record numbers, providers, diagnoses, medicines, test results, images, care and treatment (PHI).
Financial information
Billing, claims, payments; may include credit/debit card numbers and banking information for some people.
Social Security number
McKesson's notice lists Social Security among other personal identifiers that may have been involved; not confirmed for every person.
Government identification
Medicaid / Medicare / government payor ID numbers listed with insurance information.
Why this information matters
The risks below are the ones associated with the categories of information involved in this breach. This describes how exposed information can be used in general. It does not state that any of this has happened with data from this incident.
Information from one breach can sometimes be combined with information from other breaches or public sources. A name and email address on their own are limited. Paired with a date of birth from one leak and an address from a people-search site, they become enough to answer a security question or make a scam call sound informed.
Whether the data from this breach has been sold, shared, or used is not known unless a source on this page says so. Where that is documented, it appears in the "What happened" section above.
If you were affected, consider doing these things now
Practical steps for this breach, in rough order of priority. None of these require buying anything. Monitoring services, including ours, are one option among several.
- 01Follow any instructions in a notice you receive from McKesson or from a healthcare provider that uses McKesson services.
- 02If you believe you may be affected, use McKesson's dedicated call center or information-center page listed in the Sept. 8 notice to ask about complimentary IDX monitoring enrollment.
- 03Watch for phishing that references McKesson, a clinic or pharmacy you use, oncology care, or this breach.
- 04Verify any call, email, or text claiming to be from McKesson by contacting the company through a number or address you already have — not one supplied in an unexpected message.
- 05Review medical bills, insurance EOBs, and pharmacy activity for services you did not receive.
- 06Because Social Security numbers and financial details may be involved for some people, consider a credit freeze with each of the three major bureaus and check annualcreditreport.com.
- 07Enroll in any complimentary credit monitoring offered in your notice, if you receive one.
- 08Consider a personal information monitoring service.
AI Protection
Monitoring, alerts, and recovery help for what comes after a breach.
A breach puts information you can't take back into circulation. AI Protection watches for it being misused, alerts you when something changes, and helps you recover if something goes wrong. It cannot undo the breach or retrieve data an attacker already holds.
How one breach can contribute to a larger exposure footprint
A possible risk pattern, not a description of this incident. Each step is something that can happen after a breach. Nothing here states that it has happened with data from this incident.
Illustrative pattern- Step 1
One breach
A single company's records are accessed without authorization.
- Step 2
Personal information is exposed
Some categories can be changed afterward. Others, like a name or date of birth, can't.
- Step 3
It may remain accessible
Copies of breached data can persist well beyond the original incident.
- Step 4
Sources can be combined
Fragments from different breaches and public sources may be assembled into a fuller profile.
- Step 5
More targeted attempts
A fuller profile can make fraud, impersonation, phishing, or social engineering attempts more convincing.
A breach is an event. Exposure can last longer.
A password can be reset and a card reissued. Some information can't be replaced, and that is the part that stays useful to someone attempting fraud later. This does not mean fraud will occur. It means the risk does not close when the news cycle does.
Involved in this breach and hard to change
None of the categories reported in this breach are in the hard-to-change group. Changeable items like passwords and account numbers should still be addressed.
What McKesson has done so far
Only actions the company has announced or that are documented in the sources below. If something you'd expect to see isn't here, it hasn't been announced as of the last update.
Sources
Primary sources first: company disclosures, regulator and attorney general filings, SEC filings, court documents. News reporting is listed as secondary. Where reports conflict, the conflict is noted in the "What happened" section rather than resolved silently.
Last updated September 10, 2026 · First published September 10, 2026
Questions about the McKesson breach
Take control of what happens next.
Monitoring for misuse of your information, alerts when something changes, and a real person to call if something goes wrong. Plans from $7 per month. Cancel anytime.