Analyst assessment
A June 9, 2025, cyberattack disrupted the City of Thomasville’s municipal network, access to electronic records and utility-billing workflows. The city’s initial notice acknowledged suspicious activity and an outside investigation. In his July 24 open letter, Mayor Raleigh York Jr. said attackers removed and corrupted a significant amount of data across departments. We reported the initial investigation on June 12.
DysruptionHub assesses ransomware involvement with high confidence based on WXII’s reporting, the city’s account of corrupted servers and its response to extortion. INC Ransom separately claimed responsibility. Comparitech reported a claimed 250 GB theft, while Cybernews reported 260 GB. The mayor’s acknowledgment supports data removal, but does not authenticate the claimant’s volume, samples or identity; confidence in INC attribution remains low.
Operational significance
The mayor described staff losing almost all connectivity to electronic data and using workarounds to maintain essential services. Utility bills initially could not be processed; modified bills were being processed and mailed within two weeks of the attack. The city’s July 2 notice suspended automatic drafts and directed customers to other payment channels. On July 24, the mayor said bank drafts still malfunctioned for most autopay customers. His 45-day target concerned restoring standard bills and automatic drafting, rather than a confirmed deadline for recovery of every municipal system.
October 2026 reporting by the High Point Enterprise described effects on police department operations and a replacement records platform following a cyberattack. In that report and an Oct. 13 Mark43 release, Chief Dustin Carter said the old records system could not communicate with the county’s computer-aided dispatch system, forcing officers to return to headquarters to complete reports. The deployed records, mobile and analytics tools restored field-reporting capability. The accounts do not establish when the compatibility problem began or that the attack caused every limitation of the old system.
The city’s initial statement said essential public-safety services continued. The mayor said critical-system data and controls were not directly affected, with earlier cloud migrations helping protect some functions. Continued essential services therefore coexisted with disrupted administrative workflows; the evidence does not establish a loss of water delivery, a dispatch outage or interruption of emergency response.
Disclosure posture
The initial release is datelined June 10 and indexed by the city on June 11, the earliest independently supported public cyber acknowledgment. The mayor dates the attack to June 9; WXII describes discovery on June 11. The city acknowledged cyber activity before the publicly reported INC claim. The mayor’s July letter documents more extensive disruption and data removal than the initial release, when sensitive-information compromise was unresolved.
Current status
The incident remains presumed resolved. July 24, 2025, is the latest clearly dated observation of ongoing municipal disruption. The October 2026 police deployment is evidence of modernization and restored reporting capability, but supplies neither an exact restoration day nor a citywide all-clear. It does not establish uninterrupted service disruption throughout the intervening period.
Confidence and uncertainty
Confidence is high in the cyberattack, data corruption and administrative disruption because the city directly acknowledged them. The mayor’s letter also establishes the city’s report of data removal, while the affected categories, number of people and validated volume remain unknown. On July 24, the city said it was not paying a ransom or communicating with the attackers and had hired a data-recovery specialist to work on corrupted servers. That statement records its position at the time; it does not resolve the ultimate data findings.
Analytic gaps
The public record does not establish initial access, dwell time, encryption scope, the exact information removed, a final breach-notification population, total costs or the date all affected municipal services returned to normal. The police platform accounts do not identify the attack’s date or quantify lost patrol time. INC attribution and the conflicting 250 GB and 260 GB allegations remain unverified.