Back to Exposure Report
Not disclosed June 17, 2026 • Healthcare and Genomics

Baylor Genetics

Genetic data is the only category in this series that exposes people who were never customers.

Patient informationClinical laboratory data
1

What happened?

An unauthorized third party accessed portions of the Baylor Genetics network between 11 and 17 June 2026. Baylor Genetics is a clinical diagnostic laboratory specialising in genetic and genomic testing.

The number of people affected, the attacker and the specific data categories have not been established in the reporting cited here. This entry is thinner than most in this series on detail, and is included because the data type involved has properties no other category in these reports shares.

2

What data was actually inside?

Patient information held by a clinical genomics laboratory. The field-level breakdown has not been published.

What a genetics laboratory holds is structurally different from other medical data. A test result describes inherited variants, which means it describes the patient's parents, siblings and children with partial accuracy. It is also permanent in a way no other identifier is: a genome cannot be reissued, revoked or changed after exposure.

3

Who gets hurt and how?

Patients who had genetic testing ordered by a clinician, usually because somebody suspected a hereditary condition. The reason for testing is itself sensitive before any result exists.

The distinctive harm is that the affected population is larger than the patient list. A hereditary variant in one person's record is information about every blood relative, none of whom consented, were notified, or appear in any breach notification. This is the only category in this series where the people exposed cannot be enumerated even in principle.

4

What did they think they were doing right?

Clinical laboratories operate under HIPAA and CLIA and are generally among the more regulated healthcare organisations. Network segmentation between laboratory instruments, the information system and corporate IT is standard practice.

The phrase portions of the network, used in the disclosure, suggests that segmentation existed and limited the reach. That is a better outcome than most entries in this series and still leaves the question of which portions.

5

What did they not know about their own data?

Which portions, and what was in them. Six days of access produced a disclosure that describes the boundary of the intrusion without describing the contents.

Genomic data is the hardest content to inventory, because results live across laboratory information systems, sequencing output files, interpretation reports and clinician correspondence, in formats that range from structured records to free text PDFs.

A laboratory that knows which of those stores held identifiable results, for whom, can scope this in days. One that does not is reading its own files while the clock runs.

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 leak site listing appears in the available reporting. A six-day window with a defined start and end suggests detection worked and containment followed.

Genomic data has no established criminal resale market in the way card data does, which makes the motive less obvious and the consequences harder to predict than a financial breach.

7

What would have changed the outcome?

Knowing where identifiable genomic results sit, separately from the clinical records that reference them. Those are different sensitivity classes stored in different systems and they are routinely treated as one.

Second, minimising identifiable linkage. Research and quality uses rarely need the name attached to the variant, and a laboratory that separates identity from result at rest has far less to disclose when a portion of its network is reached.

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 .