HackingEducationEducationData ExfiltratedTargetedIdentity (basic)Financial accountLowContained

New Hampshire PublicRadio

bd_edc27cf8d6c6397e · schema v1 · pii pii-v1

Severity

Low

Discovered

May 6, 2024

Filed

Aug 20, 2024

To disclose

15 weeks

Affected · nationwide

22724 in this filing

Linked

5 filings

Confidence

66%

Full breach record for New Hampshire PublicRadio →2 incidents on file

New Hampshire Public Radio (NHPR) disclosed an external system breach (hacking) occurring between April 6, 2024, and May 6, 2024. NHPR discovered suspicious activity on May 6, 2024. The incident affected 227 individuals, including 24 Maine residents. Compromised data included names and bank account numbers. NHPR engaged forensic specialists, notified federal law enforcement, and provided one year of credit monitoring via Experian to affected individuals. Notices were sent on August 20, 2024.

J jump to incidentP pin to compareR raw source

Maine clockDiscovered May 6, 2024 → Filed with AG Aug 20, 2024106d ✗ ME AG >90d15 weeks discovery → filing

⚠ unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.

Incident timeline

undetected · 30 days

discovery → filing · 15 weeks / 106 days

Apr 6, 2024

Begins

May 6, 2024

Discovered

Aug 20, 2024

Filed

vs. sector median

+7 wks slower

This filing is one of 5 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Siteakirabd_73e2b0c7ff5153252024-05-31 · +80dVerified by operator

Regulatory filings (3) · sorted by filing gap

Vermont State AGbd_1a7ccb3fa3dd85cb2024-08-20Verified
Massachusetts State AGbd_5517f88a943d6a972024-08-20Verified by operator
Massachusetts State AGbd_391ab861258f03772023-07-03 · +414dVerified by operator

Name: New Hampshire PublicRadio
norm: new hampshire publicradio
Domain: nhpr.org

Name: New Hampshire PublicRadio
norm: new hampshire publicradio
Domain: nhpr.org
Industry: Educationllm

Discovered: May 6, 2024
Breach occurred: Apr 6, 2024 – May 6, 2024
Undetected for: 30 daysoccurrence → discovery
Materiality determined: —
Notification sent: Aug 20, 2024
Affected individuals: 227state + nationwide
Data types: Identity (basic)Financial account
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1078 Valid Accounts
Threat actor: External
Regulator citations: Notified federal law enforcement
Initial access: exploit_public_facing

During the incident: Took steps to secure its systems
Launched an investigation into the nature and scope of the event with the assistance of third-party forensic specialists
Engaged a data review vendor to conduct a comprehensive review of the affected files
Performed additional work to verify the results
Notified federal law enforcement regarding the event
Changes made: Implemented additional security measures to further protect against similar incidents occurring in the future
Working to implement additional safeguards and training to its employees
Providing access to credit monitoring services for one (1) year, through Experian, to individuals whose personal information was potentially affected by this incident, at no cost to these individuals
Providing impacted individuals with guidance on how to better protect against identity theft and fraud
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 15 weeks(106 days from discovery to filing)
Compliance flags: ME AG >90d · 106dLeak >30d
Discovery-date grounding: unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.
Clock breakdown: Statute Window Elapsed Threshold Status
Maine
Discovered: May 6, 2024
→ Filed with AG: Aug 20, 2024
106d 90 days ME AG >90d

Statute	Window	Elapsed	Threshold	Status
Maine	Discovered: May 6, 2024 → Filed with AG: Aug 20, 2024	106d	90 days	ME AG >90d

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 3 states

View merged incident ↗

Massachusetts State AGJul 3 · first

Vermont State AG+414d

Massachusetts State AG+414d

Maine State AG+414d · this page

Pattern: first filing Jul 3 (MA), last Aug 20 (ME) — a 414-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://www.maine.gov/agviewer/content/ag/985235c7-cb95-4be2-8792-a1252b4f8318/f09fdeda-f98e-4fa5-adb6-fd15a0c5aab1.html
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 20, 2024
Raw hash: af32b28fc904bdba0307f24e125d2c23ddccf4ae95943cd5874adc6b8cde9e0b

Linked disclosures

Ransomware claims (1)

Regulatory filings (3) · sorted by filing gap

Reporting entityNew Hampshire PublicRadio

Victim entityNew Hampshire PublicRadio

Incidentdiscovered May 6, 2024

Stated responseTook steps to secure its systems

ComplianceME AG >90d

Extraction provenanceno artifact recorded

Source provenancewww.maine.gov