DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed8 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedsamsamhigh sensitivity
Merged incident · 8 filings

LABORATORY CORPORATION OF AMERICA HOLDINGS — August 2018 breach

Clustered 8 filings across 8 jurisdictions · filing window Jul 13, 2019 → Jul 17, 2019. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

10,251,784

First → last filing

Jul 13, 2019 → Jul 17, 2019

Merge confidence

100%

incident inc_9a799a9a50c1400f · merged by human · confidence 100%

Part of the Retrieval-Masters Creditors Bureau, Inc supply-chain incident (2019) — at least 17 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe hacking. Intrusion Aug 1, 2018–Mar 30, 2019, discovered May 14, 2019 — the first regulatory filing landed 60 days later (flagged late). 10,251,784 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
60days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
4days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dOregon✗ OR AG >45dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 1, 2018breach begins
May 14, 2019discovered
notification delay · 60 days
Jul 13, 2019first filing
Jul 17, 2019most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUL 13WA AGWA AG noticefirst filing · 18,330 WA residentsday 0
  2. JUL 13HHS OCRHHS OCR noticestates nationwide total 10,251,784day 0
  3. JUL 13MT AGMT AG notice4,823 MT residentsday 0
  4. JUL 15SC AGSC AG notice366,110 SC residents+2d
  5. JUL 15CA AGCA AG noticeno count stated+2d
  6. JUL 16NH AGNH AG notice303 NH residents+3d
  7. JUL 17MA AGMA AG notice750 MA residents+4d
  8. JUL 17OR AGOR AG noticemost recent · no count stated+4d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 1, 2018 – Mar 30, 2019
WA AG
Discovered
May 14, 2019· 286d undetected
WA AG + MT AG + SC AG +3
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
WA AG + HHS OCR + MT AG +4
Attack vector
Third-Party / Supply Chain
WA AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

10,251,784

Sum of filed state slices

390,316· 3.8% of stated

96% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US10,251,784
SC366,110
WA18,330
MT4,823
MA750
NH303

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing8 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 25, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

4 days

Cadence

~1 / 0.6d

vs. multi-state median

2.0× faster

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.