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

Texas Tech University Health Sciences Center — September 2024 breach

Clustered 15 filings across 10 jurisdictions · filing window Nov 25, 2024 → Apr 27, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 filings

States

10

Affected · reported

813,892

First → last filing

Nov 25, 2024 → Apr 27, 2026

Merge confidence

100%

incident inc_98fdc9678ee34ae3 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings. The filings describe unauthorized access. Intrusion Sep 17, 2024–Sep 29, 2024, discovered Sep 1, 2024 — the first regulatory filing landed 85 days later (flagged late). 813,892 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 4 more. Notifications rolled out on a 518-day schedule across 15 filings beginning Nov 25, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
85days

Discovered → first regulatory filing

Discovery variance
106days

Range of discovered_at dates across filings

Filing span
518days

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 >180dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 494dOregon✗ OR AG >45dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 17, 2024breach begins
Sep 1, 2024discovered · members disagree
notification delay · 85 days
Nov 25, 2024first filing
Apr 27, 2026most 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. NOV 25HHS OCRHHS OCR noticefirst filing · states nationwide total 650,000day 0
  2. JAN 24MT AGMT AG notice82 MT residents+60d
  3. JAN 24CA AGCA AG noticeno count stated+60d
  4. JAN 24VT AGVT AG noticeno count stated+60d
  5. JAN 24ME AGME AG noticestates nationwide total 533,874+60d
  6. JAN 24NH AGNH AG notice18 NH residents+60d
  7. JAN 24IN AGIN AG noticestates nationwide total 533,874+60d
  8. NOV 13MD AGMD AG notice145 MD residents+353d
  9. APR 9WA AGWA AG notice511 WA residents+500d
  10. APR 24ME AGME AG noticestates nationwide total 813,892+515d
  11. APR 24NH AGNH AG notice7 NH residents+515d
  12. APR 24OR AGOR AG noticestates nationwide total 813,892+515d
  13. APR 24VT AGVT AG notice29 VT residents+515d
  14. APR 24CA AGCA AG noticeno count stated+515d
  15. APR 27TX AGTX AG noticemost recent · states nationwide total 813,892+518d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 17, 2024 – Sep 29, 2024
MT AG
Discovered
Sep 1, 2024MT AG + VT AG + NH AGSep 17, 2024WA AGSep 29, 2024MD AG + OR AGDec 16, 2024ME AG + TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
HHS OCR + CA AG + MD AG +6
Attack vector
Unauthorized Access
HHS OCR

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)

813,892

Sum of filed state slices

739,599· 90.9% of stated

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

US813,892
TX738,506
WA511
IN252
MD145
MT82
ME56
VT29
NH18

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 filing15 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 10, 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

518 days

Cadence

~1 / 37d

vs. multi-state median

64.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.