DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed9 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 filings

University of St. Thomas - Houston — July 2025 breach

Clustered 9 filings across 8 jurisdictions · filing window Mar 9, 2026 → May 28, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

26,644

First → last filing

Mar 9, 2026 → May 28, 2026

Merge confidence

100%

incident inc_fb6e2e173d9b4b16 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Jul 25, 2025–Aug 12, 2025, discovered Aug 12, 2025 — the first regulatory filing landed 209 days later (flagged late). 26,644 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 6 more. Notifications rolled out on a 80-day schedule across 9 filings beginning Mar 9, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
209days

Discovered → first regulatory filing

Discovery variance
224days

Range of discovered_at dates across filings

Filing span
80days

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 clocksTexas✗ TX AG >30dWashington✗ WA AG >90dMaine⏱ ME AG >30d · 63dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Jul 25, 2025breach begins
Aug 12, 2025discovered · members disagree
notification delay · 209 days
Mar 9, 2026first filing
May 28, 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. MAR 9TX AGTX AG noticefirst filing · no count statedday 0
  2. MAY 26VT AGVT AG notice6 VT residents+78d
  3. MAY 26ME AGME AG notice3 ME residents+78d
  4. MAY 26WA AGWA AG notice516 WA residents+78d
  5. MAY 26IN AGIN AG noticestates nationwide total 26,644+78d
  6. MAY 26NE AGNE AG notice16 NE residents+78d
  7. MAY 26MA AGMA AG notice48 MA residents+78d
  8. MAY 27NH AGNH AG notice6 NH residents+79d
  9. MAY 28TX AGTX AG noticemost recent · states nationwide total 26,644+80d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 25, 2025
ME AG
Discovered
Aug 12, 2025WA AG + NE AG + NH AGFeb 12, 2026TX AGMar 24, 2026ME AG + TX AGfilings disagree on discovery
Data types
Authentication · Education · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
TX AG + VT AG + WA AG +4
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)

26,644

Sum of filed state slices

24,790· 93.0% of stated

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

US26,644
TX24,158
WA516
MA48
IN37
NE16
VT6
NH6
ME3

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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 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

80 days

Cadence

~1 / 10d

vs. multi-state median

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