Back to Exposure Report
Not disclosed October 12, 2026 • Healthcare

Healthcare Highways

Patients choose a doctor. The network behind the doctor chooses itself.

Protected health information
1

What happened?

Healthcare Highways, a Texas-based medical provider network company, announced a data security incident in the same reporting window as Photon Health and Any-Time Home Care.

The specific data categories, the number of people affected, the intrusion date and the attacker have not been established in the reporting cited here. This entry is deliberately thin and the gaps are marked rather than filled. It is included because the organisation type is worth examining even where the incident detail is not yet available.

2

What data was actually inside?

Not established. Reporting at the time of writing describes a data security incident without a published field list.

What a provider network holds is not in doubt even where this incident's detail is. Network companies sit between employers, plans and clinicians, which means membership data, eligibility, claims routing and the provider relationships that reveal what care a member sought and from whom.

3

Who gets hurt and how?

Plan members, who selected an employer or a plan rather than a network administrator. The relationship is three steps removed from anything the patient agreed to.

The specific exposure in a network breach is relational rather than clinical. Knowing that a named person is a member of a particular network, saw a particular specialist and had a claim routed on a particular date describes their care without containing a single clinical note.

4

What did they think they were doing right?

Provider networks exist because negotiating rates and routing claims across thousands of clinicians is work that neither an employer nor a patient can do. Consolidating it is the efficiency the system is built on.

The consequence is concentration. A network aggregates member data across many employers and many providers, so a single incident reaches populations that have no connection to each other except that the same intermediary handled their claims.

5

What did they not know about their own data?

Unanswerable from the public record at this stage, and this entry does not pretend otherwise.

The structural observation holds regardless. Intermediary organisations in healthcare accumulate data from every party they connect, which makes their inventory harder to maintain than that of any single provider and their breach notifications slower to scope.

Three healthcare organisations disclosed in one week. For each, the question that determines how fast patients learn anything is whether somebody had already established what the affected systems contained.

If you handle patient data, could you identify within 24 hours exactly which records were accessed in a breach?

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

6

What does attribution look like the morning after?

No group has been named and no attribution appears in the available reporting.

Healthcare is the most consistently targeted sector in this series. The reason is not that attackers prefer medical data ideologically, it is that it is comprehensive, monetisable in several distinct markets, and held by organisations with uneven security budgets.

7

What would have changed the outcome?

For this incident, too little is established to say. When the scope is published this entry will be worth revisiting.

The general point for intermediaries: the data arrives from every party you connect, it accumulates faster than anybody maps it, and the gap between a disclosure and a scope statement is set entirely by whether that map existed before the incident.

Gyazo 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 .