Simms Fishing Products reported a data breach to the Montana Attorney General. The breach was reported on 2021-02-05. The breach occurred from 10/29/2020 to 11/24/2020. 68 Montana residents were affected.
Affected (this filing): 68
Clustered 2 filings across 2 jurisdictions · filed Feb 5, 2021. View entity profile → Other incidents for this victim →
incident inc_5fbab69609be4732 · 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
Oct 29, 2020
When the intrusion reportedly occurred, per the linked filings
Jan 8, 2021
Reported by MAINE AG filing
Simms Fishing Products reported a data breach to the Montana Attorney General. The breach was reported on 2021-02-05. The breach occurred from 10/29/2020 to 11/24/2020. 68 Montana residents were affected.
Affected (this filing): 68
Simms Fishing Products, LLC reported a data breach impacting 14 Maine residents after malicious code was injected into its e-commerce website. The breach occurred between October 29, 2020, and November 24, 2020, and was discovered on January 8, 2021. The compromised information includes names combined with financial account numbers or credit/debit card numbers and their associated security codes or PINs. Customers were notified on February 5, 2021.
Affected (this filing): 14
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.