DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 6 filings

West Texas Health — September 2025 breach

Clustered 6 filings across 4 jurisdictions · filing window Nov 17, 2025 → Mar 16, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

75,858

First → last dated filing

Nov 17, 2025 → Mar 16, 2026

Merge confidence

100%

incident inc_3c14e711e9204d9f · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe unauthorized access. Intrusion Sep 12, 2025–Oct 3, 2025, discovered Oct 3, 2025 — the first regulatory filing landed 45 days later; 1 later filing was flagged late. 75,858 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 119-day schedule across 3 dated filings beginning Nov 17, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
45days

Discovered → first regulatory filing

Discovery variance
126days

Range of discovered_at dates across filings

Filing span
119days

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 clocksMassachusetts✗ MA AG >90dTexas✓ TX CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 12, 2025breach begins
Oct 3, 2025discovered · members disagree
notification delay · 45 days
Nov 17, 2025first dated filing
Mar 16, 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 about this breach

  1. NOV 17NE AGNE AG noticefiling day not on record · no count stated—
  2. NOV 17IN AGIN AG noticefirst filing · states nationwide total 2,138day 0
  3. NOV 17NE AGNE AG noticefiling day not on record · no count stated—
  4. FEB 23NE AGNE AG noticefiling day not on record · no count stated—
  5. FEB 23MA AGMA AG notice10 MA residents+98d
  6. MAR 16TX AGTX AG noticemost recent · states nationwide total 75,858+119d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 12, 2025 – Oct 3, 2025
NE AG
Discovered
Oct 3, 2025NE AG + MA AGFeb 6, 2026TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
NE AG + MA AG + TX AG
Attack vector
Unauthorized Access
NE 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)

75,858

Sum of filed state slices

74,469· 98.2% of stated

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

US75,858
TX74,456
MA10
IN3

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 filing6 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

119 days

Cadence

~1 / 59.5d

vs. multi-state median

19.8× 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.