Smithfield Specialty Foods Group LLC reported a data breach to the Montana Attorney General. The breach was reported on 2023-06-29. The breach occurred from 11/24/2021 to 12/14/2022. 55 Montana residents were affected.
Affected (this filing): 55
Clustered 2 filings across 2 jurisdictions · filing window Jun 29, 2023 → Jul 3, 2023. View entity profile → Other incidents for this victim →
incident inc_8a5c1bcf2ce64aa4 · 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.
MT NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 24, 2021
When the intrusion reportedly occurred, per the linked filings
Jun 7, 2023
Reported by NEW HAMPSHIRE AG filing
Smithfield Specialty Foods Group LLC reported a data breach to the Montana Attorney General. The breach was reported on 2023-06-29. The breach occurred from 11/24/2021 to 12/14/2022. 55 Montana residents were affected.
Affected (this filing): 55
Smithfield Specialty Foods Group LLC reported a data breach affecting its third-party web hosting provider, CommerceV3, Inc. Unauthorized access occurred between November 24, 2021, and December 14, 2022, impacting customer data from smithfieldmarketplace.com and thepeanutshop.com. Smithfield was notified on June 7, 2023. Approximately 209 New Hampshire residents were affected. Smithfield suspended the affected hosting service and provided credit monitoring services to affected individuals.
Affected (this filing): 209
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.