Back to Exposure Report
80 million records claimed, disputed October 14, 2026 • Healthcare Diagnostics

Ampath Laboratories

A database row and a human being are not the same unit, and the gap between them is the whole dispute.

NamesID numbersContact detailsMedical aid informationPayment information
1

What happened?

Ampath Laboratories, one of South Africa's largest private pathology providers, detected and contained a cybersecurity incident affecting part of its IT environment on 2 October 2026. On 13 October the threat actor ByteToBreach posted on a hacker forum claiming it had compromised Ampath, publishing screenshots of the intrusion.

Ampath confirmed the cyberattack on 14 October and disputed the headline figure. The group claimed data from at least ten databases, including a laboratory admissions table holding 80 million records. Ampath responded that the number appears to describe database entries rather than unique individuals.

2

What data was actually inside?

Ampath's notice confirms that names, ID numbers, contact details, and medical aid and payment information may have been accessed. The company states there is no evidence that medical records, diagnoses, test results or banking information were compromised.

South African ID numbers are the field that carries the most weight. Unlike an account number, a South African ID number encodes date of birth, gender and citizenship status in its own digits, which means a single leaked identifier reconstructs three additional attributes without any other record being involved. Medical aid membership adds the insurer relationship on top of that.

3

Who gets hurt and how?

Patients who used a pathology lab, which is to say people who were referred there by a doctor and had no say in which provider processed the sample.

The confirmed data supports identity fraud and medical aid fraud rather than clinical disclosure. An ID number paired with medical aid membership is enough to attempt claims against someone else's benefits, and the victim usually discovers it when a legitimate claim is declined because the annual limit has already been consumed.

4

What did they think they were doing right?

Detection and containment worked. The incident was identified on 2 October and contained, which is faster than most of the entries in this series, and an investigation with independent forensic specialists and legal advisers began immediately.

Ampath also notified South Africa's Information Regulator under Section 22 of the Protection of Personal Information Act and issued notification to potentially affected people. Procedurally this is close to the textbook response. The problem arrived from a different direction.

5

What did they not know about their own data?

The dispute over the number is the tell. Ampath is arguing that 80 million refers to database entries rather than unique individuals, and the argument is probably correct, because a laboratory admissions table records one row per admission and a patient generates many admissions over years of care.

But notice what that argument requires. To say with confidence how many people sit behind 80 million rows, somebody has to deduplicate the table and resolve the identifiers. If that work had already been done, the answer would be a number rather than a characterisation. Instead the public position is that the figure is misleading, which is true and also not the same as knowing the real one.

This is the quiet cost of counting records instead of people. The attacker gets to publish a number on day one. The organisation spends weeks earning the right to correct it.

If your business runs on databases, you probably have similar records, customer data, credentials, financial information. Do you know what's actually in yours?

Not sure where to start? How to find sensitive data across your estate

6

What does attribution look like the morning after?

ByteToBreach claimed the intrusion on a forum with screenshots. Ampath has confirmed an attack but not the scope claimed, and the gap between those two statements is where the investigation now lives.

Under POPIA, notification to the Information Regulator is required where there are reasonable grounds to believe personal information has been accessed by an unauthorised person. Ampath has met that threshold and filed. What it has not yet been able to do is tell each affected person what of theirs was involved, which is the part that depends on resolving the table, not on the filing.

7

What would have changed the outcome?

A current map of which tables held identifiers, which held clinical results, and how many distinct people the identifiers resolve to. Ampath's claim that results were not taken is credible and important, and it is far stronger when it arrives as an inventory fact rather than as an absence of evidence.

The organisations that survive an inflated claim intact are the ones that can answer it the same week with a number of their own. That capacity is built before the forum post, or it is not available when it is needed. The Quest Diagnostics entry in this series shows the same clock running in a different country.

Ampath Laboratories found out the hard way.

Your team could spend the next 6 months rebuilding systems, notifying customers, and answering legal questions. Or you could spend 24 hours finding out what's actually at risk.

Want to understand the process first? Read our guide to sensitive data discovery .