Newcourse Communications, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2023-03-09. The breach occurred from 4/27/2022 to 5/3/2022. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Mar 9, 2023 → Mar 14, 2023. View entity profile → Other incidents for this victim →
incident inc_e9ee8d532e754863 · merge_method human · 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
Apr 27, 2022
When the intrusion reportedly occurred, per the linked filings
Feb 15, 2023
Reported by MAINE AG filing
Newcourse Communications, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2023-03-09. The breach occurred from 4/27/2022 to 5/3/2022. 1 Montana residents were affected.
Affected (this filing): 1
Newcourse Communications reported an external system breach that occurred between April 27, 2022, and May 3, 2022. The incident was discovered on February 15, 2023. The breach compromised the names and financial account numbers or credit/debit card numbers (with security codes) of 8,373 individuals. The company began notifying affected individuals on March 10, 2023, and offered 12 months of complimentary credit monitoring services through IDX.
Affected (this filing): 8,373
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.