FEDERALMalwareHealthcareHealthcareRansomwareData EncryptedLowResolved

LABCORP HOLDINGS INC.

bd_069b4b2979bf9f36 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jul 1, 2018

Filed

Feb 24, 2026

To disclose

—

Affected

Not disclosed

Confidence

70%

Full breach record for LABCORP HOLDINGS INC. →

In July 2018, the Company experienced a ransomware incident that affected certain diagnostic information technology systems and temporarily affected other IT systems used in Company-wide operations. Investigation concluded that the ransomware did not and could not transfer patient or client data outside Company systems, with no theft or misuse of patient or client data. The incident was not material to the Company. Disclosure appears in Item 1C of an Annual Report (10-K).

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 93 months / 2795 days

Jul 1, 2018

Begins

Jul 1, 2018

Discovered

Feb 24, 2026

Filed

Tracked as a single-filing incident — the only disclosure on record for this event so far.No incident reportedView incident

Name: LABCORP HOLDINGS INC.
norm: labcorp holdings
SEC CIK: 920148

Name: LABCORP HOLDINGS INC.
norm: labcorp holdings
SEC CIK: 920148
Industry: Healthcarellm

Discovered: Jul 1, 2018
Breach occurred: Jul 1, 2018
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: —
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for Impact
Threat actor: ExternalFinancial

During the incident: An investigation determined that the ransomware did not and could not transfer patient or client data outside of Company systems
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statementThis record

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://www.sec.gov/Archives/edgar/data/920148/000092014826000111/lh-20251231.htm
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Feb 24, 2026
Raw hash: 816eadd36094b75b55fa65b6864f064ca277ad5e1e0fc7f75cafcacdf31cc1dc

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html3.0 MB

Download View at source

Reporting entityLABCORP HOLDINGS INC.

Victim entityLABCORP HOLDINGS INC.

Incidentdiscovered Jul 1, 2018

Stated responseAn investigation determined that the ransomware did not and could not transfer patient or client data outside of Company systems

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing