FMT Consultants LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2025-04-23 and was reported on 2025-06-23. 1 Indiana residents were affected. 502 individuals affected in total.
Affected (this filing): 502
Clustered 2 filings across 2 jurisdictions · filed Jun 23, 2025. View entity profile → Other incidents for this victim →
incident inc_7e86ae7efcc74ee0 · 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
Apr 23, 2025
When the intrusion reportedly occurred, per the linked filings
May 1, 2025
Reported by NEW HAMPSHIRE AG filing
FMT Consultants LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2025-04-23 and was reported on 2025-06-23. 1 Indiana residents were affected. 502 individuals affected in total.
Affected (this filing): 502
FMT Consultants, LLC reported a data security incident where an unknown actor gained unauthorized access to its network, affecting the name and Social Security numbers of former employees. FMT detected suspicious activity on May 1, 2025, engaged forensic investigators, and notified one New Hampshire resident on June 23, 2025. The company offered 24 months of credit and identity monitoring services.
Affected (this filing): 1
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.