Clustered 3 filings across 3 jurisdictions · filing window Feb 11, 2023 → Sep 11, 2023. View entity profile → Other incidents for this victim →
incident inc_14fc5d0334bf437e · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
ME NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 23, 2023 → Feb 7, 2023
When the intrusion reportedly occurred, per the linked filings
Feb 5, 2023
Reported by MAINE AG filing
B&G Foods, Inc. manufactures, sells, and distributes a portfolio of shelf-stable and frozen foods, and household products in the United States, Canada, and Puerto Rico.
Feb 12, 2023
Reported by NEW HAMPSHIRE AG filing
B&G Foods, Inc. notified the New Hampshire Attorney General of a cybersecurity incident occurring between January 23 and February 7, 2023. An unauthorized third party gained access to systems via indiscriminate cyber-attacks, accessing employee data files containing personal information. B&G discovered the intrusion on February 12, 2023. The breach affected 3 New Hampshire residents. B&G engaged third-party experts, notified law enforcement, implemented MFA, and offered credit monitoring services to affected individuals.
B&G Foods, Inc. reported an external system breach (hacking) occurring between January 23, 2023, and February 7, 2023, discovered on February 5, 2023. The incident affected 918 individuals, including 112 Maine residents. Personal information compromised included names and Social Security Numbers. B&G Foods provided written notification and offered 24 months of credit monitoring through Experian.
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.
Affected (this filing): 3
Affected (this filing): 918