Clustered 3 filings across 3 jurisdictions · filing window May 31, 2024 → Aug 20, 2024. View entity profile → Other incidents for this victim →
incident inc_913e3f71816f45ec · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
ME VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 6, 2024 → May 6, 2024
When the intrusion reportedly occurred, per the linked filings
May 6, 2024
Reported by VERMONT AG filing
Since 1981, New Hampshire Public Radio has shaped the media lands cape in the Granite State and beyond. The files of the organizati on will be in public soon. You could see and download them here o n our blog. Financial and accounting data, grants and much other information. Everything is about 35GB.
Jul 8, 2024
Reported by MAINE AG filing
New Hampshire Public Radio (NHPR) disclosed a cybersecurity incident where an unknown actor accessed its network between April 6, 2024, and May 6, 2024. NHPR engaged forensic specialists and a data review vendor. The incident involved unauthorized access to systems containing personal information. NHPR reported the incident to federal law enforcement and regulators, implemented additional security measures, and offered 12 months of credit monitoring via Experian.
New Hampshire Public Radio reported a data breach to the Maine Attorney General, stating that an external system breach (hacking) occurred between April 6, 2024, and May 6, 2024. The breach was discovered on July 8, 2024, and affected 24 Maine residents. The company began notifying affected individuals on August 20, 2024.
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.
Affected (this filing): 24