Clustered 3 filings across 3 jurisdictions · filing window Nov 29, 2017 → Dec 11, 2017. View entity profile → Other incidents for this victim →
incident inc_12a9491a1f224bd9 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
CA MT WA
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 1, 2017
When the intrusion reportedly occurred, per the linked filings
Oct 6, 2017
Reported by CALIFORNIA AG, WASHINGTON AG filings
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.
Combat Brands reported a data breach to the Montana Attorney General. The breach was reported on 2017-11-29. The breach occurred from 7/1/2017 to 10/6/2017. 32 Montana residents were affected.
Affected (this filing): 32
Combat Brands, LLC disclosed a cyber-attack affecting customer payment data (card numbers, CVVs, names, addresses) from July 2015 to October 2017. Malware was identified on October 6, 2017. The company engaged forensic investigators and removed the malware.
Combat Brands, LLC, a business sector entity reported a malware incident to the Washington Attorney General. The organization became aware of the incident on 2017-10-06 and filed notice on 2017-12-11. 956 Washington residents were affected. 66 days elapsed between awareness and notification. 828 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 956