Confirmed breach. Intrusion Jan 16, 2024–Feb 4, 2024, discovered Feb 1, 2024 — the first regulatory filing landed 57 days later. 3,317 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksVermont⏱ VT AG >14 bdayHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
3,317
Data types
2
Identity (basic) · PII
Jurisdictions
2
TX VT
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 16, 2024 → Feb 4, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Feb 1, 2024
Reported by VERMONT AG filing
57 days
🍁Vermont State AGFirst filinglinked via same-victim cross-source · 100%
Rehabilitation Hospital of Mesquite notified consumers of a data breach where unauthorized access occurred between Jan 16 and Feb 4, 2024. Patient information, including names and other data elements, was accessed. The hospital engaged forensic investigators, isolated systems, and offered one year of credit monitoring.
VT AG >14 bday
⭐TEXASHHS OCRMost recentlinked via same-victim cross-source · 100%
Mesquite Rehabilitation Institute reported to HHS on 2024-03-29 a Hacking/IT Incident affecting 3317 individuals. Breached information located on Network Server. The incident involved ransomware encrypting PHI, including names, DOB, SSN, driver's license, and treatment data. The entity offered credit monitoring and implemented security safeguards.
Affected (this filing): 3,317
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.