GLOBALClaimed by BianLianFirst sightinglinked via shared-victim match · 100%
Posted to leak site Apr 22, 2024bd_7206089cdd8d5f6e
Texas Retina Associates, with 13 offices throughout the state and 17 physicians, is Texas' largest retina clinic group.
Clustered 4 filings across 3 jurisdictions · filing window Apr 22, 2024 → Jul 12, 2024. View entity profile → Other incidents for this victim →
incident inc_f7600ec11a90434d · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
TX VT
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 8, 2023
When the intrusion reportedly occurred, per the linked filings
Mar 27, 2024
Reported by VERMONT AG filing
Texas Retina Associates, with 13 offices throughout the state and 17 physicians, is Texas' largest retina clinic group.
Texas Retina Associates, with 13 offices throughout the state and 17 physicians, is Texas' largest retina clinic group.
Texas Retina Associates reported to HHS on 2024-06-21 a Hacking/IT Incident affecting 312,867 individuals. Breached information located on Network Server. The incident involved a ransomware attack encrypting PHI (clinical and demographic data). The entity provided credit monitoring and implemented additional safeguards.
Texas Retina Associates notified consumers of a data breach where an unauthorized actor accessed systems starting Oct 8, 2023. The incident was discovered on March 27, 2024. Affected data included names and government IDs (SSN/DOB). The company engaged forensic investigators and offered credit monitoring.
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.
Affected (this filing): 312,867