Crossroads Trading Co. Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2025-03-25. The breach occurred on 02/15/2025. 31 Montana residents were affected.
Affected (this filing): 31
Clustered 2 filings across 2 jurisdictions · filed Mar 25, 2025. View entity profile → Other incidents for this victim →
incident inc_4036db51e51b4a59 · 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
Feb 15, 2025
When the intrusion reportedly occurred, per the linked filings
Feb 15, 2025
Reported by NEW HAMPSHIRE AG filing
Crossroads Trading Co. Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2025-03-25. The breach occurred on 02/15/2025. 31 Montana residents were affected.
Affected (this filing): 31
Crossroads Trading Co., Inc. reported a ransomware incident on March 25, 2025, affecting 32 New Hampshire residents. On February 15, 2025, an unauthorized third party gained access to the company's server and encrypted data. The company secured the network, engaged forensic investigators and a cyberthreat firm, and notified the FBI. Personal information of NH residents was encrypted. Identity theft protection services were offered to affected individuals.
Affected (this filing): 32
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.