Northwood League, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2024-12-09. The breach occurred on 07/01/2024. 14 Montana residents were affected.
Affected (this filing): 14
Clustered 2 filings across 2 jurisdictions · filing window Dec 9, 2024 → Dec 10, 2024. View entity profile → Other incidents for this victim →
incident inc_0434eb10e01c4985 · 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 VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 1, 2024
When the intrusion reportedly occurred, per the linked filings
Jul 1, 2024
Reported by VERMONT AG filing
Northwood League, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2024-12-09. The breach occurred on 07/01/2024. 14 Montana residents were affected.
Affected (this filing): 14
Northwoods League, Inc. disclosed a July 2024 data breach affecting its ticketing service. An unknown threat actor exploited the checkout tool, potentially accessing credit card numbers and PII (names, addresses, emails, phones) for purchases through October 9, 2024. The company replaced the checkout tool, engaged forensic investigators, and partnered with IDX for consumer support. No specific affected individual count was provided.
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.