Confirmed breach. Intrusion Nov 14, 2023, discovered Nov 14, 2023 — the first regulatory filing landed 93 days later (flagged late). 2,264,157 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 >45 bdayFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
2,264,157
Data types
4
Identity (basic) · Government ID · Health (basic)
Jurisdictions
2
IN VT
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Nov 14, 2023
When the intrusion reportedly occurred, per the linked filings
Medical Management Resource Group, LLC (dba American Vision Partners) notified patients of a cybersecurity incident detected on November 14, 2023. Unauthorized parties accessed patient data including names, DOBs, SSNs, medical records, and insurance info. Affected individuals were offered 2 years of credit monitoring. The incident is currently contained.
VT AG >45 bday
🏎️Indiana State AGMost recentlinked via multistate filing link · 100%
Medical Management Resource Group, LLC, dba American Vision Partners reported a data breach to the Indiana Attorney General. The breach occurred on 2023-11-14 and was reported on 2024-02-15. 2,281 Indiana residents were affected. 2,264,157 individuals affected in total.
Affected (this filing): 2,264,157
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.