DisclosureLens
State AGConfirmed9 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Merged incident · 9 filings

Texas Tech University Health Sciences Center El Paso — September 2024 breach

Clustered 9 filings across 9 jurisdictions · filing window Jan 24, 2024 Nov 13, 2025. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

868,133

First → last filing

Jan 24, 2024 Nov 13, 2025

Merge confidence

100%

incident inc_37e1b0e1cd5040de · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Sep 17, 2024–Sep 29, 2024, discovered Sep 1, 2024. 868,133 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 2 more. Notifications rolled out on a 659-day schedule across 9 filings beginning Jan 24, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
107days

Range of discovered_at dates across filings

Filing span
659days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont VT AG >45 bdayWashington WA AG >90dOregon OR AG ≤45dFull clock table in Litigation Timeline

Incident timeline

Sep 17, 2024breach begins
Sep 1, 2024discovered · members disagree
Jan 24, 2024first filing
Nov 13, 2025most 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. JAN 24NE AGNE AG noticefirst filing · no count statedday 0
  2. JAN 1IL AGIL AG noticeno count stated+343d
  3. JAN 24MT AGMT AG notice96 MT residents+366d
  4. JAN 24VT AGVT AG noticeno count stated+366d
  5. JAN 24CA AGCA AG noticeno count stated+366d
  6. JAN 24OR AGOR AG noticestates nationwide total 868,133+366d
  7. JAN 24IN AGIN AG noticestates nationwide total 868,133+366d
  8. JAN 24WA AGWA AG notice889 WA residents+366d
  9. NOV 13MD AGMD AG noticemost recent · no count stated+659d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 17, 2024
NE AG
Discovered
Sep 1, 2024MT AG + VT AGSep 29, 2024IL AG + WA AG + MD AGDec 17, 2024NE AG + OR AGfilings disagree on discovery
Data types
Identity (basic) · PII · PHI · Government ID · Health (basic)
MT AG + VT AG + WA AG +2
Attack vector
Unauthorized Access
MT 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)

868,133

Sum of filed state slices

1,737· 0.2% of stated

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

US868,133
WA889
IN752
MT96

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 filing9 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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
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

659 days

Cadence

~1 / 82.4d

vs. multi-state median

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