Clustered 3 filings across 3 jurisdictions · filing window Oct 13, 2025 → Jan 5, 2026. View entity profile → Other incidents for this victim →
incident inc_51922f5d4ca54066 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
ME NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 11, 2025 → Oct 13, 2025
When the intrusion reportedly occurred, per the linked filings
Oct 13, 2025
Reported by NEW HAMPSHIRE AG filing
Designs for Vision, Inc. specializes in high-quality magnificatio n and LED headlights for dental, medical, and low vision applicat ions. We will upload about 50gb of corporate documents soon. Lots of pr oject information, a bit of personal information, credit cards de tails and other financial and accounting information, contracts a nd agreements, NDA, etc.
Dec 4, 2025
Reported by MAINE AG filing
Designs For Vision, Inc. notified the New Hampshire Attorney General on January 5, 2026, of unauthorized access to its computer systems occurring between October 11 and 13, 2025. The breach affected 6 New Hampshire residents, exposing names and financial account information. DVI engaged in investigation, secured systems, and provided 12 months of credit monitoring via Kroll to affected individuals.
Designs For Vision Inc. (Bohemia, NY) reported an external system breach (hacking) that occurred on October 11, 2025 and was discovered on December 4, 2025. Six Maine residents were affected. Written notifications were sent on January 5, 2026. Kroll identity theft protection services were offered to affected individuals.
Affected (this filing): 6
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): 6