McKesson Data Breach (August 2026)
McKesson, the Texas healthcare and pharmaceutical distributor, disclosed a cybersecurity incident involving third-party applications and data exfiltration in August 2026, and Have I Been Pwned has since verified 6,404,340 records from data ShinyHunters published, covering patients, staff, marketing campaign recipients and healthcare provider contacts.
- Organization
- McKesson
- Sector
- Healthcare
- Country
- United States, TX
- Incident date
- August 21, 2026
- Disclosed
- August 28, 2026
- Records affected
- 6.4 million
- Attack type
- Undisclosed
- Threat actor
- ShinyHunters
- Status
- Confirmed
- Dates of birth
- Email addresses
- Employers
- Genders
- Names
- Personal health data
- Phone numbers
- Physical addresses
- The breach date recorded in the Have I Been Pwned entry. ShinyHunters told BleepingComputer its data theft ran over four days from this date to August 25.
- McKesson discovers the cybersecurity incident, per its Form 8-K. ShinyHunters told BleepingComputer it contacted the company after finishing the data theft that day, demanded a $55,236,150 ransom and gave McKesson 72 hours to respond.
- McKesson files a Form 8-K with the U.S. Securities and Exchange Commission, per the filing, and announces a cybersecurity incident involving third-party applications and the exfiltration of data, per The HIPAA Journal's report.
- ShinyHunters' leak site listing for McKesson Corporation is first recorded by ransomware.live.
- McKesson updates its notice to say the exfiltrated data was associated with a subset of customers in its Oncology & Multispecialty and Medical-Surgical business units, per The HIPAA Journal and SecurityWeek.
- The deadline ShinyHunters set for McKesson to contact the group before it made the stolen information public, per SecurityWeek and the group's listing as recorded by ransomware.live.
- Have I Been Pwned loads the data ShinyHunters published, covering 6,404,340 unique email addresses, per its entry.
What Happened
McKesson disclosed the incident in a Form 8-K filed with the U.S. Securities and Exchange Commission on August 28, 2026, saying it discovered "a cybersecurity incident affecting its information systems" on August 25 and had not determined that the incident is material. According to The HIPAA Journal, McKesson announced the incident the same day, explaining that it had launched an investigation following "a cybersecurity incident involving third-party applications and unauthorized access and exfiltration of data."
In an August 29 update, McKesson said the exfiltrated data was associated with "a subset of customers within our Oncology & Multispecialty and Medical-Surgical business units," SecurityWeek reported, along with the company's statements that the unauthorized access had been disrupted and that affected individuals would be offered complimentary credit monitoring and identity protection. A McKesson spokesperson told SecurityWeek the company has "reasonable assurance of no ongoing unauthorized activity" in its systems.
ShinyHunters told BleepingComputer that it gained access through voice phishing attacks on multiple McKesson employees, which compromised their Okta single sign-on accounts and let the group into the company's Salesforce and Snowflake environments, where it took about 1TB of data between August 21 and August 25. The group claims the Snowflake data holds approximately 284 million patient-related data records, a raw count of lines rather than of people, and that the stolen information includes names, addresses, dates of birth, Social Security numbers, Medicaid numbers, medical record numbers and medication and allergy information. BleepingComputer states that it has not independently verified these claims.
According to the Have I Been Pwned entry, the group went on to publish a substantial corpus of data it alleged came from McKesson, relating to marketing campaign recipients, patients, staff and healthcare provider contacts. Have I Been Pwned added 6,404,340 unique email addresses from that corpus on September 10, 2026 and flags the breach as sensitive, so it is not publicly searchable: people have to sign in to its dashboard to check their own address.
What Was Exposed
8 classes of data across 6,404,340 records, per Have I Been Pwned, McKesson breach entry: dates of birth, email addresses, employers, genders, names, personal health data, phone numbers and physical addresses.
Names, dates of birth, genders, addresses, phone numbers and email addresses sitting beside personal health data let a fraudster pose as a pharmacy, clinic or insurer that already knows a person's medical details, which makes a request for payment or insurance information far more believable.
What to Do If You Are Affected
The full sequence, and what to do in what order, is in what to do after a data breach.
What Is Not Known Yet
How the attackers got into the third-party applications, which types of data McKesson itself says were taken, and how many people it will notify. McKesson had not publicly confirmed the scale of the breach when The Register reported on the published data on September 10, 2026.
Sources
- Have I Been Pwned, McKesson breach entry
- U.S. Securities and Exchange Commission, McKesson Corporation Form 8-K, August 28, 2026
- BleepingComputer, "McKesson discloses breach after ShinyHunters claims patient data theft", August 28, 2026
- SecurityWeek, "McKesson Confirms Data Breach as Attacker Deadline Looms", August 31, 2026
- The HIPAA Journal, "ShinyHunters Claims Theft of 284M Records from Healthcare Giant McKesson", August 31, 2026
- The Register, "ShinyHunters expose 6.4M in attack on medical supplier McKesson", September 10, 2026
- ransomware.live, McKesson Corporation leak site listing, August 28, 2026

Daniel Reyes
Daniel Reyes is a CISSP who spent twelve years in security operations, most recently leading a detection and response team for a mid-sized healthcare group in Texas. He reviews every resource and breach report on Cyber Security Firms for technical accuracy before it publishes.
Most of the people he has trained arrived having been told too much: a dozen acronyms, six vendors, and no clear idea which risk was theirs. His approach is to explain what an attack actually does before naming the tool that stops it, on the basis that most breaches start with something a reader could have recognised.