Confirmed breach. Intrusion May 11, 2025, discovered May 11, 2025 — the first regulatory filing landed 234 days later (flagged late). 8,845 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 claimConfirmedEnforced
Affected (total reported)
8,845
Data types
—
Jurisdictions
2
IN VT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
May 11, 2025
When the intrusion reportedly occurred, per the linked filings
Cyrus D. Mehta & Partners PLLC reported a data breach to the Indiana Attorney General. The breach occurred on 2025-05-11 and was reported on 2025-12-31. 29 Indiana residents were affected. 8,845 individuals affected in total.
Affected (this filing): 8,845
54 days
🍁Vermont State AGMost recentlinked via multistate filing link · 95%
Cyrus D. Mehta & Partners PLLC, an immigration law firm, notified consumers of a data incident discovered on May 11, 2025. An unauthorized third party accessed systems and removed data, potentially exposing names, addresses, dates of birth, SSNs, and government IDs. The firm secured systems, reset passwords, engaged forensic specialists and law enforcement, and offered credit monitoring services.
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.