MalwareGovernmentGovernmentRansomwareData ExfiltratedData EncryptedPIIIdentity (basic)LowContained

Union County, Ohio

bd_2902fd2c45650c27 · schema v1 · pii pii-v1

Severity

Low

Discovered

May 18, 2025

Filed

Sep 24, 2025

To disclose

18 weeks

Affected

21state residents only

Linked

3 filings

Confidence

65%

Full breach record for Union County, Ohio →

Union County, Ohio notified individuals of a ransomware incident detected on May 18, 2025. Unauthorized access occurred between May 6 and May 18, 2025. Personal information was accessed and exfiltrated. The County engaged forensic consultants and law enforcement, reset passwords, and enhanced security monitoring. Notices were sent beginning August 25, 2025.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 12 days

discovery → filing · 18 weeks / 129 days

May 6, 2025

Begins

May 18, 2025

Discovered

Sep 24, 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

Maine State AGbd_e13fd488600b1f812025-09-24Verified
New Hampshire State AGbd_c253643f9c1cb7922025-10-06 · +12dVerified

Name: Union County, Oregon
norm: union county oregon

Name: Union County, Ohio
norm: union county ohio
Industry: Governmentllm

Discovered: May 18, 2025
Breach occurred: May 6, 2025 – May 18, 2025
Undetected for: 12 daysoccurrence → discovery
Materiality determined: —
Notification sent: Aug 25, 2025
Affected individuals: 21state-resident count only
Data types: PIIIdentity (basic)
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: The County will notify all appropriate state regulators regarding this incident

During the incident: Launched an investigation with assistance from nationally recognized third-party cybersecurity and data forensics consultants
Alerted federal law enforcement
Changes made: Deployed security tools to enhance detection and accelerate response to cyber incidents
Continuing to actively monitor its network using end point detection tools
Conducted an enterprise-wide password reset
Strengthened restrictions for external network access
Evaluating steps to further bolster our cyber defenses
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 18 weeks(129 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 ↗

Maine State AGSep 24 · first

Montana State AGSep 24 · first · this page

New Hampshire State AG+12d

Pattern: first filing Sep 24 (ME), last Oct 6 (NH) — a 12-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://dojmt.gov/wp-content/uploads/2025/09/Consumer-notification-letter-61.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Sep 24, 2025
Raw hash: d6a0922e314aa1e915f8b8673459b27ca60a1c32d3ff904bfd16a54f0df7f628

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityUnion County, Oregon

Victim entityUnion County, Ohio

Incidentdiscovered May 18, 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 provenancedojmt.gov