Molecular Testing Labs Data Breach
The 2025 Molecular Testing Labs data breach involved a ransomware incident at a data-hosting and security vendor retained by CareNexa. According to the organization's public notice, unauthorized activity affected MTL systems and data between March 7 and March 13, 2025.
This scope reflects unique email identifiers supplied to help notify malware victims; it does not establish an individual-victim or user total.
Review Device and Account Security
Check whether your email identifier appears in this malware exposure
Check my emailExposed Data Types
1 sensitive3- Medical information
- Names
- Physical addresses
About This Record
CareNexa operates as Molecular Testing Labs, a provider of clinical and diagnostic laboratory services.
When did the breach occur?
A forensic investigation determined that the incident occurred from March 7 through March 13, 2025. After learning of the event, Molecular Testing Labs investigated with cybersecurity specialists and notified law enforcement. Letters were mailed to identified affected individuals on April 23, 2025.
What information may have been affected?
According to the organization's public notice, the information may have included names, addresses and information related to medical tests, depending on the individual. Not every category applied to every person.
How many people were affected?
The U.S. Department of Health and Human Services breach record reports 7,711 affected individuals.
What did the organization do?
Molecular Testing Labs said it investigated with a national cybersecurity firm, notified law enforcement and strengthened its security posture. At the time of the public notice, the organization said it had received no reports of misuse, identity theft or fraud related to the incident.
What should affected people do?
Notice recipients should review health-insurance explanations, medical records and account activity for unfamiliar transactions. Anyone who finds an unfamiliar medical service or bill should contact the provider and insurer.
Verification and editorial method
LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.
Report missing or incorrect information
