Ferrara Candy Company reported a data breach to the Montana Attorney General. The breach was reported on 2022-04-29. The breach occurred from 10/2/2021 to 10/9/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Apr 29, 2022. View entity profile → Other incidents for this victim →
incident inc_3104dddcb90c483e · merge_method llm · confidence 45%
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.
Identity (basic) · Government ID
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 2, 2021
When the intrusion reportedly occurred, per the linked filings
Mar 30, 2022
Reported by MAINE AG filing
Ferrara Candy Company reported a data breach to the Montana Attorney General. The breach was reported on 2022-04-29. The breach occurred from 10/2/2021 to 10/9/2021. 1 Montana residents were affected.
Affected (this filing): 1
Ferrara Candy Company reported a data breach to the Maine Attorney General, stating that an external system breach (hacking) occurred between October 2, 2021, and October 9, 2021. The breach was discovered on March 30, 2022. The compromised information includes names and Social Security numbers. One Maine resident was affected out of a total of 8,359 individuals. The company provided written notification to the affected individual on April 29, 2022, and offered 12 months of complimentary identity restoration, fraud consultation, and credit monitoring services through Equifax.
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.