Montagut & Sobral PC reported a data breach to the Indiana Attorney General. The breach occurred on 2024-06-24 and was reported on 2024-09-19. 19 Indiana residents were affected. 23,839 individuals affected in total.
Affected (this filing): 23,839
Clustered 2 filings across 2 jurisdictions · filing window Sep 19, 2024 → Oct 8, 2024. View entity profile → Other incidents for this victim →
incident inc_e1d43955108d497a · merge_method deterministic · confidence 95%
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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 24, 2024
When the intrusion reportedly occurred, per the linked filings
Jun 24, 2024
Reported by NEW HAMPSHIRE AG filing
Montagut & Sobral PC reported a data breach to the Indiana Attorney General. The breach occurred on 2024-06-24 and was reported on 2024-09-19. 19 Indiana residents were affected. 23,839 individuals affected in total.
Affected (this filing): 23,839
Montagut & Sobral, PC notified the NH Attorney General of a data breach detected on June 24, 2024. An unauthorized party copied personal information of approximately 3 NH residents. Data included names, DOB, phone, address, email, driver's license, passport, SSN, and financial info. The firm engaged cybersecurity experts, contacted law enforcement, enhanced security controls, and offered credit monitoring.
Affected (this filing): 3
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.