MalwareGovernmentGovernmentRansomwareRansom DemandedData ExfiltratedSupply Chain (3P Vendor)Customer Data InvolvedIdentity (basic)Government IDMediumContained

Pike County, Ohio

bd_5585d3b1918366e3 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Apr 28, 2025

Filed

Jul 28, 2025

To disclose

13 weeks

Affected

1state residents only

Linked

3 filings

Confidence

66%

Full breach record for Pike County, Ohio →

Pike County, Ohio, filed a supplemental notice regarding a ransomware attack on its third-party IT provider. The incident, discovered on April 28, 2025, resulted in the unauthorized access and exfiltration of files containing names, driver's license numbers, and Social Security numbers. One New Hampshire resident was identified as affected. The County engaged forensic consultants, notified law enforcement, and is offering one year of complimentary credit monitoring via Experian.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 13 weeks / 91 days

Apr 28, 2025

Discovered

Jul 7, 2025

Scope determined

Jul 28, 2025

Filed

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

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Massachusetts State AGbd_868262ed3b3108aa2025-07-29 · +1dVerified
Vermont State AGbd_b3e66579ae4b42cf2025-07-24 · +4dCandidate

Name: Pike County, Ohio
norm: pike county ohio

Name: Pike County, Ohio
norm: pike county ohio
Industry: Governmentllm

Discovered: Apr 28, 2025
Materiality determined: Jul 7, 2025
Notification sent: Jul 24, 2025
Affected individuals: 1state-resident count only
Data types: Identity (basic)Government ID
Data elements: Social Security number
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 ChannelT1195 Supply Chain Compromise
Threat actor: ExternalFinancial
Regulator citations: Notified federal law enforcementNotified all appropriate state regulators
Initial access: supply_chain

During the incident: Launched an investigation with assistance from nationally recognized third-party cybersecurity and data forensics consultants
Notified federal law enforcement
Began an extensive review of those files to determine what information may have been involved and who may have been affected
Began the process of confirming the security of its network and initiated an investigation
Notified all appropriate regulators
Changes made: Continuing to evaluate additional steps that may be taken to further bolster its defenses
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 13 weeks(91 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Vermont State AGJul 24 · first

New Hampshire State AG+4d · this page

Massachusetts State AG+5d

Pattern: first filing Jul 24 (VT), last Jul 29 (MA) — a 5-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://mm.nh.gov/files/uploads/doj/remote-docs/pike-county-ohio-20250728.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 28, 2025
Raw hash: f93aa59cd93e30bb2f7e09c54e3501eb9f998990ec86e1b9722a078c4b85214d

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityPike County, Ohio

Victim entityPike County, Ohio

Incidentdiscovered Apr 28, 2025

Stated responseLaunched an investigation with assistance from nationally recognized third-party cybersecurity and data forensics consultants

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov