DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed14 records · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedqilinhigh sensitivity
Merged incident · 14 records

COVENANT HEALTH — May 2025 breach

Clustered 14 records across 10 jurisdictions: 13 filings and 1 leak-site claim · filing window Jul 11, 2025 → Jan 5, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 records

States

10

Affected · reported

478,188

First → last dated filing

Jul 11, 2025 → Jan 5, 2026

Merge confidence

100%

incident inc_4d98d36388434085 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion May 18, 2025–May 27, 2025, discovered May 26, 2025 — the first regulatory filing landed 46 days later; 2 later filings were flagged late. 478,188 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 2 more. Notifications rolled out on a 178-day schedule across 11 dated filings beginning Jul 11, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
46days

Discovered → first regulatory filing

Discovery variance
198days

Range of discovered_at dates across filings

Leak precedence
17days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
178days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayTexas✗ TX AG >30dMaine⏱ ME AG >30d · 46dMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 18, 2025breach begins
May 26, 2025discovered · members disagree
notification delay · 46 days
Jul 11, 2025first dated filing
Jan 5, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. MAY 25Leak siteqilin postfirst record · attacker claim · unverifiedday 0
  2. JUL 11MA AGMA AG notice15,860 MA residents+47d
  3. JUL 11ME AGME AG noticestates nationwide total 7,864+47d
  4. JUL 11HHS OCRHHS OCR noticestates nationwide total 7,864+47d
  5. JUL 11NH AGNH AG notice2,269 NH residents+47d
  6. DEC 31NH AGNH AG notice154,188 NH residents+220d
  7. DEC 31ME AGME AG noticestates nationwide total 478,188+220d
  8. DEC 31NE AGNE AG noticefiling day not on record · 41 NE residents—
  9. DEC 31VT AGVT AG noticeno count stated+220d
  10. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  11. JAN 2SC AGSC AG notice1,338 SC residents+222d
  12. JAN 2MT AGMT AG notice76 MT residents+222d
  13. JAN 2CA AGCA AG noticeno count stated+222d
  14. JAN 5TX AGTX AG noticemost recent · states nationwide total 478,188+225d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 18, 2025
ME AG
Discovered
May 26, 2025ME AG + NH AG + NE AG +5Dec 10, 2025SC AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
MA AG + ME AG + NH AG +8
Attack vector
Unauthorized Access
ME 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)

478,188

Sum of filed state slices

457,133· 95.6% of stated

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

US478,188
ME284,529
NH154,188
MA15,860
SC1,338
TX1,101
MT76
NE41

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 claim1 member

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

Press / market report

No press coverage linked yet.

State AG / regulator filing13 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 Oct 22, 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

178 days

Cadence

~1 / 17.8d

vs. multi-state median

29.7× slower

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.