Clustered 2 filings across 2 jurisdictions · filing window Jun 1, 2026 → Jun 8, 2026. View entity profile → Other incidents for this victim →
incident inc_507232cef4194a1d · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
Identity (basic)
MA VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 23, 2025 → Jan 20, 2026
When the intrusion reportedly occurred, per the linked filings
Jun 23, 2025
Reported by MASSACHUSETTS AG filing
Alexes Hazen, MD, PLLC notified Massachusetts and Rhode Island residents of unauthorized access to computer systems between June 23, 2025, and January 20, 2026. The incident may have exposed patient names. The practice offered credit monitoring and identity restoration services via Experian. Approximately 5 Rhode Island residents were identified as potentially impacted.
Alexes Hazen, MD PLLC reported a data breach to the Vermont Attorney General. The breach was reported to the AGO on 2026-06-08. The reporting organization type is Health Care. 8 Vermont residents were affected. Categories of data breached: Social Security Numbers, Government ID Numbers, Financial Account Codes, Credit and Debit Account Info, Health Records.
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.