Walsworth Publishing Company reported a data breach to the Montana Attorney General. The breach was reported on 2022-01-20. The breach occurred on 10/21/2021. 4 Montana residents were affected.
Affected (this filing): 4
Clustered 2 filings across 2 jurisdictions · filing window Jan 20, 2022 → Jan 24, 2022. View entity profile → Other incidents for this victim →
incident inc_ad50bd2641c64841 · 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
Oct 21, 2021
When the intrusion reportedly occurred, per the linked filings
Oct 21, 2021
Reported by NEW HAMPSHIRE AG filing
Walsworth Publishing Company reported a data breach to the Montana Attorney General. The breach was reported on 2022-01-20. The breach occurred on 10/21/2021. 4 Montana residents were affected.
Affected (this filing): 4
Walsworth Publishing Company notified the New Hampshire Attorney General of a data security incident involving unauthorized access to an employee email account. Discovered on October 21, 2021, the breach exposed personal information including names, SSNs, health data, bank account info, and credentials. One NH resident was affected. Walsworth engaged forensic investigators, secured the email platform, and provided credit monitoring and ID theft recovery services to the affected individual.
Affected (this filing): 1
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.