Frankel Loughran Starr & Vallone LLP reported a data breach to the Indiana Attorney General. The breach occurred on 2025-12-12 and was reported on 2026-02-26. 1 Indiana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Feb 26, 2026 → Mar 2, 2026. View entity profile → Other incidents for this victim →
incident inc_5ea93242ff2c461e · 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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 12, 2025
When the intrusion reportedly occurred, per the linked filings
Dec 12, 2025
Reported by NEW HAMPSHIRE AG filing
Frankel Loughran Starr & Vallone LLP reported a data breach to the Indiana Attorney General. The breach occurred on 2025-12-12 and was reported on 2026-02-26. 1 Indiana residents were affected.
Affected (this filing): 1
Frankel Loughran Starr & Vallone LLP (FLSV) notified the New Hampshire Attorney General of a data security incident. On December 12, 2025, unusual network activity disrupted access to FLSV's systems. An investigation determined that certain files were accessed without authorization, potentially exposing Social Security numbers and financial account numbers. Approximately 8 New Hampshire residents were notified. FLSV engaged cybersecurity experts, implemented safeguards, and provided 12 months of credit monitoring and identity protection services through Kroll. The FBI was notified.
Affected (this filing): 8
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.