Horace Mann Life Insurance Company reported a data breach to the Montana Attorney General. The breach was reported on 2025-09-09. The breach occurred from 10/29/2023 to 11/02/2023. 353 Montana residents were affected.
Affected (this filing): 353
Clustered 2 filings across 2 jurisdictions · filed Sep 9, 2025. View entity profile → Other incidents for this victim →
incident inc_8d041dac7ba84cde · merge_method human · 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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 29, 2023
When the intrusion reportedly occurred, per the linked filings
Nov 2, 2023
Reported by CALIFORNIA AG filing
Horace Mann Life Insurance Company reported a data breach to the Montana Attorney General. The breach was reported on 2025-09-09. The breach occurred from 10/29/2023 to 11/02/2023. 353 Montana residents were affected.
Affected (this filing): 353
Horace Mann Life Insurance Company reported a ransomware incident affecting its third-party service provider, Infosys McCamish Systems, LLC. Unauthorized activity occurred between October 29, 2023, and November 2, 2023, when systems were encrypted. The investigation determined that data was subject to unauthorized access and acquisition, including names and other personal information. The incident has been contained and remediated. Affected individuals are offered 24 months of credit monitoring.
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.