The McKesson breach: the data is out, and 6.4 million addresses are in it

McKesson found an intrusion on 25 August 2026. Three weeks later the group behind it published the files. What landed holds 6,404,340 unique email addresses — a long way from the 284 million records that were advertised, and the first figure in this story anyone can check. Including whether yours is in there.

ByNikita Lushpanov· Chief Product Officer ·LinkedIn
Quick answer

The data attributed to the McKesson incident was published on 10 September 2026 and catalogued by the breach-checking services shortly after, so an email address can be tested against it now. The set carries 6,404,340 unique addresses along with names, dates of birth, phone numbers, home addresses, employers and personal health data. That is a fraction of the 284 million records the attackers advertised in August, and Social Security numbers are not among the fields catalogued in it. If your address is in there, the exposure is identity and health information rather than a password: freeze your credit file at all three bureaus, read the statements your insurer sends, and treat any email offering to check the breach for you as hostile until you have checked it yourself.

What is established vs what was claimed

The left column is what can be pointed at: McKesson’s own disclosure, plus the corpus published on 10 September and the fields catalogued in it. The right is the account the group gave reporters in August, before anyone could open the files. Where nobody has said anything, the row says so instead of filling the gap.

QuestionWhat is establishedWhat ShinyHunters claimed
That something happenedYes. McKesson discovered a cybersecurity incident on 25 August 2026 and disclosed it to the SEC in an 8-K filing. Its customer cybersecurity notice ties the unauthorised access to third-party applications, and the data taken to a subset of customers in its Oncology & Multispecialty and Medical-Surgical business units.The extortion group ShinyHunters says it was behind it and went public the same week the filing appeared.
How the intruders got inNot stated. McKesson has not described the method or named the applications involved.Phone calls to staff — the caller talks an employee through signing in on a page that is not the real one, then walks in with the code. The group says this got it into single sign-on accounts and from there into two cloud platforms the company uses for customer records and data warehousing.
How much was takenThe published set is the only part anyone can measure: 6,404,340 unique email addresses, with names, dates of birth, contact details, employers and health-related fields attached to them. McKesson itself has put no number on the incident.Roughly a terabyte, pulled out over four days between 21 and 25 August, amounting to 284 million records.
How many people that isStill nobody has published a headcount. What is countable is 6.4 million addresses, and that is a ceiling rather than a total: people hold several inboxes, and the same person can appear under more than one.Unknown, and the group said so itself at the time: it had not finished going through the files and did not know how many unique people were in them.
What kind of dataIn the published set: names, dates of birth, email addresses, phone numbers, physical addresses, employers, genders and personal health data. Social Security numbers are not among the fields catalogued in it.Also Social Security numbers, patient and medical record identifiers, and clinical details such as medications, allergies and diagnoses.
A ransom demandNot addressed in the filing.A demand of just over $55 million with a 72-hour deadline, which the group says the company did not respond to.
Whether the data is publicYes, since 10 September 2026. The corpus was published and has been catalogued by the breach-checking services people use, which is why an email address can be tested against it now.The group threatened release for a fortnight before it happened.
Notification lettersMcKesson has not published who is being written to or when. Its notice describes the data as belonging to a subset of customers in two of its business units, which is narrower than the set that ended up online.Not applicable — attackers do not send notification letters.

Sources: McKesson’s 8-K filing with the SEC and the company’s customer cybersecurity notice; the corpus published on 10 September 2026 and the fields catalogued from it by the breach databases our checker queries; reporting by BleepingComputer, CyberInsider, Cybernews and DataBreaches.net, 28 August to 10 September 2026. Status as of 20 September 2026; this page will be updated if the company publishes a count of its own or begins notifying people.

1. What changed on 10 September

For two weeks this story ran on an SEC filing and an attacker’s press release. The filing was short: third-party applications compromised, unauthorised access and exfiltration of data, an early investigation, no determination of materiality. Everything with a number in it came from the extortion group. Then the group published, and the argument moved from what people were saying to what anyone can open. The set attributed to the incident carries 6,404,340 unique email addresses and was catalogued by the breach-checking services within hours. That does three things at once: it makes the incident checkable by ordinary people, it puts the first verified figure on the record, and it quietly deflates the figure that had been travelling. Both columns below still matter — the company has confirmed less than the files now show, and the files show far less than the attackers advertised.

2. 284 million records, 6.4 million addresses

The two numbers are not in competition; they count different things, and only one of them can be checked. 284 million was a count of rows claimed before anybody outside the attack had seen the data, with a caveat from the group itself that mostly did not travel: it had not finished going through the files and did not know how many people were in them. 6.4 million is a count of distinct email addresses in what actually got published. A person can hold several addresses, so even that is a ceiling rather than a headcount — but it is a ceiling roughly forty times below the headline. This is the clearest example we have of why a record count should never be read as a number of patients. If you see the August figure still quoted as people, the source has added a word its own source did not use.

3. Why this can involve you when you have never heard the name

McKesson is not a consumer brand. It is one of the largest distributors of medicines in the country, and around that it runs services attached to prescriptions and patient support for manufacturers, pharmacies and providers. Individuals end up in those systems through their pharmacy and their clinic rather than by signing up for anything, which is why not recognising the name rules nothing out. The published set reads exactly like that: patients next to staff, provider contacts and people who only ever received a marketing email. Our guide to medical data breaches covers why health records need a different response from a leaked password.

4. The impersonation problem just got a better hook

One detail from the attackers’ own account deserved more attention than the record count: the operation involved a domain registered to look like a McKesson claims site. Impersonating the company was part of how the intrusion worked, and that instinct is now pointed at the public with better material than before. Until 10 September, a message offering to tell you whether you were affected was self-evidently false, because nothing had been released. Now checking is real, which makes a fake check plausible. The test is still the route rather than the wording: real notifications arrive by post, do not require a click to find out whether you are affected, and never ask for your Social Security number back. Our breach-letter guide goes through what a genuine one contains.

5. What the published fields actually call for

Match the response to what is in the set rather than to the headline. There are no passwords in it, so a password rotation is not the job. There are no Social Security numbers among the catalogued fields either, which takes tax-refund fraud off the immediate list. What there is: a name, a date of birth, a current address, a phone number, an employer and health information — the combination used to open credit somewhere else in your name, and to make a cold call sound like it came from your clinic. So: freeze your credit file at all three bureaus, turn on two-factor authentication on your email, and read the explanation-of-benefits statements your insurer sends, querying any treatment you did not receive. Health records cannot be frozen and a date of birth cannot be reissued, which is why noticing misuse early is the whole defence.

6. The lawyer emails arrived within a day

Ademi LLP announced an investigation on 29 August, one day after the disclosure, and it was not the last firm to do so — that is the reflex now for any breach with a recognisable name attached, and publication of the data will have accelerated it. It is worth knowing what the stage means. A firm announcing an investigation is looking for clients. It is not a filed case, not a certified class, and not money waiting to be claimed. If a case is filed and eventually settles, the notice reaches you from a court-appointed administrator, usually by post, and claiming is free. That takes years, not weeks. Until then, anything asking for a fee or for your Social Security number to “register your claim” is a scam that the news cycle handed a script to. Our list of settlements actually taking claims is checked against the official administrator sites.

7. The part that outlasts this breach

The data that made this set useful was never held only by McKesson. A current address, a phone number and a list of relatives are what turn a stolen identity record into a call somebody believes, and those are published and sold openly by people-search and data-broker sites regardless of who gets breached next. Removing them is the one step here whose effect outlasts the news, and it needs repeating rather than doing once, because brokers rebuild profiles from public records within weeks. For the general version of the response, our post-breach guide covers it in seven steps.

Check the set — and the 499 sites that never needed a breach

The published corpus can be searched by email address, and our scan starts there. Then it looks at the part that gets forgotten: the home address, phone number and relatives published about you by 499 broker and people-search sites, breach or no breach — the detail that makes a stolen record usable in the first place. Both in one pass, free.

Check my email and my exposure — free →
Common questions

The McKesson breach, answered

How do I check whether my data was in the McKesson breach?

Search your email address. The corpus was published on 10 September 2026 and catalogued shortly after, so the breach-checking services that index public sets — ours included — can now tell you whether an address appears in it. That is a change from the first two weeks of this story, when nothing had been released and anybody offering to check was guessing. One caveat worth holding on to: the set contains 6.4 million addresses out of an incident the attackers described as far larger, so a clean result means your address is not in the published portion, not that nothing about you was taken.

Were 284 million patients affected?

No, and the published data is now the clearest argument against that framing. 284 million was a count of records claimed by the attackers before anyone could see the files; what actually landed carries 6,404,340 unique email addresses. Records are rows, and one person generates rows in ordering, dispensing and support systems over and over. A figure written as patients when the source said records has had a word added to it. Use 6.4 million addresses as the checkable number and treat the rest as an unverified claim.

Does the published data include Social Security numbers?

Not in the fields catalogued in it. What the set carries is names, dates of birth, email addresses, phone numbers, home addresses, employers, genders and personal health data. The attackers had claimed Social Security numbers and medical record identifiers as well, and that part has not turned up in what was released. It matters for what you do next: without a Social Security number in play, tax-refund fraud is not the thing to chase, while a date of birth paired with a current address is exactly what an application for credit in your name needs.

Is the McKesson breach real?

Yes, on both counts now. The company found an intrusion on 25 August 2026 and told the SEC that third-party applications were compromised and data was taken. Three weeks later the group claiming the attack published a corpus, and it holds a real set of personal and health data rather than a recycled collection. What never got established is the headline: the scale and the exact contents described in August were the attackers’ own account, and the published files came in far smaller than that account promised.

Why would a drug distributor have my medical information?

Because McKesson sits behind the pharmacy counter rather than in front of it. It is one of the largest distributors of medicines in the United States, and around that business it runs services tied to prescriptions and patient support for manufacturers, pharmacies and clinics. Records about individuals can end up in those systems without anyone ever having heard the name, which is why "I have no relationship with McKesson" does not rule you out. The published set bears that out — it mixes patients with staff, provider contacts and people who only ever received a marketing email from one of the business units.

I got an email about the McKesson breach. Should I click it?

No. The group behind this registered a domain built to look like a McKesson claims site as part of the attack itself, which tells you how central impersonation is here, and publication has handed that wave a better hook: now that checking is genuinely possible, "check whether you are affected" is a line that sounds reasonable. Judge a message by how it reached you rather than by how it looks. A real notification arrives by post, explains what happened without needing you to click to find out, and never asks for your Social Security number back. If you want to check, type the address of a service you already trust rather than following a link someone sent you.

My address is in it. What should I actually do this week?

Freeze your credit file at Equifax, Experian and TransUnion. It is free, it takes about ten minutes at each, and with a date of birth and a current address circulating it is the measure that blocks rather than reports. Then read the explanation-of-benefits statements your insurer sends and query any care you did not receive, because health data has no bureau to freeze it at and noticing misuse early is the whole defence. Third, expect the calls: someone holding your date of birth, your employer and a health detail can make a cold call sound like a follow-up from your clinic.

Law firms are advertising. Is there money to claim?

Not from an advertisement, whatever stage the litigation has reached. Ademi LLP announced an investigation on 29 August, a day after the disclosure, and it was not the last firm to do so. A firm announcing an investigation is looking for clients — it is not a filed case, not a certified class, and not money waiting to be collected. If a case is filed and eventually settles, notice reaches you from a court-appointed administrator, usually by post, and claiming is free. That is measured in years. Anything asking for a fee or for your Social Security number to "register your claim" is a scam the news cycle handed a script to.

Should I change my passwords?

It will not hurt, but it is not the point here. No passwords were in the published set. What is in it is identity and health information, which is not used to log in as you — it is used to open credit elsewhere in your name, or to make a call sound legitimate because the person on the line knows your date of birth and where you work. Turning on two-factor authentication on your email is a better use of ten minutes than a password rotation, because your inbox is what a stranger holding your personal details would try to take over first.

A letter is the slow way to find out

The set is public and searchable now. Check your address against it, then see which broker sites are publishing the address and phone number that make a stolen record usable. Free, about a minute.

Run my free exposure scan →