Hufcor Holdings, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2023-01-18. The breach occurred from 11/4/2021 to 2/2/2022. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Jan 18, 2023. View entity profile → Other incidents for this victim →
incident inc_458840d4fc7d42ba · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 4, 2021
When the intrusion reportedly occurred, per the linked filings
Mar 2, 2022
Reported by MAINE AG filing
Hufcor Holdings, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2023-01-18. The breach occurred from 11/4/2021 to 2/2/2022. 1 Montana residents were affected.
Affected (this filing): 1
Hufcor Holdings, Inc. reported an external system breach that occurred between November 4, 2021, and February 2, 2022, discovered on March 2, 2022. The incident compromised the names and financial account numbers of 5,054 individuals. In response, the company provided written notification to affected consumers and offered 12 months of complimentary credit monitoring and identity protection services.
Affected (this filing): 5,054
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.