Skip to content

Fort Smith network security event disrupts city services

Summary

City of Fort Smith logo

Fort Smith’s August 2026 network intrusion disrupted municipal systems and led to confirmed data theft, publication and a ransom demand. Public payment services returned, while police records-search restrictions were still documented Oct. 26. Material disruption is assessed as presumed resolved; full internal recovery and Interlock attribution remain unconfirmed.

Key facts

Timeline

  • Incident start:
    ? Earliest known or assessed start of malicious activity or incident activity.
  • First public signal:
    ? Earliest public indication of an outage, disruption, closure or other observable incident impact. The signal does not need to mention cybersecurity.
  • First public cyber evidence:
    ? Earliest credible public information connecting the incident or disruption to malicious cyber activity.
  • Official cyber disclosure:
    ? First official acknowledgment by the affected organization or an authoritative public body that the incident was cyber-related.
  • Last impact seen:
    ? Latest public indication that disruption, degraded operations, recovery work or unresolved impact was still ongoing.

Primary victim organization

Impacted locations

Critical infrastructure sector

Incident characteristics

Assessments

DD-CIT assessment

The organization publicly identifies the event as cyber-related. The organization publicly documents the resulting service disruption.

Attack mechanisms

Data impacts

  • Data theft or exfiltration

    Data was copied, transferred, downloaded, or otherwise removed from the affected environment by an unauthorized party.

  • Data publication or leak

    Stolen, exposed, or otherwise compromised data was publicly released, posted, distributed, or offered for download.

  • Data unavailable

    Authorized users could not access required data because of the incident, even when the data was not encrypted, deleted, or destroyed.

Operational impacts

  • Internal systems unavailable

    Internal business, administrative, operational, or staff-facing systems were unavailable.

  • Payment processing disruption

    The organization could not process, receive, issue, reconcile, or record payments normally.

  • Records access disruption

    Staff, customers, patients, students, residents, or other users could not access records or case information normally.

  • Manual workaround required

    Staff or users had to rely on paper, telephone, in-person, offline, or other manual processes.

  • Partial service outage

    A service, system, platform, or operational capability remained available only in part or with significant limitations.

  • Government services disrupted

    Public administrative, licensing, permitting, court, tax, records, benefits, or other government services were materially affected.

Extortion indicators

  • Ransom demand

    The victim received a demand for payment in exchange for restoring access, decrypting systems, preventing disclosure, or stopping another threatened action.

  • Leak-site listing

    The victim was listed on a threat actor or ransomware data-leak site as an alleged target or nonpaying victim.

  • Payment denied

    An authoritative source stated that no ransom or extortion payment was made.

Incident narrative

Analyst assessment

Fort Smith disclosed Aug. 16 a network security event that disrupted municipal systems and services. The city initially said Sept. 15 that an unauthorized actor entered through police systems and stole data. In an Oct. 8 response published Oct. 9, it corrected that preliminary finding: the intrusion began in the broader city network, then spread to police and other systems. It continued to report containment, with investigation and recovery underway.

The city’s Sept. 23 statement, reproduced by Talk Business & Politics, confirmed that a portion of city data had been taken and subsequently released. It said current financial, accounting, customer-data and human-resources systems were not involved and that it had found no evidence customer or resident credit-card or banking information was compromised. Those findings do not exclude other categories of stolen information; review and potential notification work continued.

In a Sept. 24 interview with 5NEWS, Dingman confirmed a ransom demand and said the city neither negotiated nor paid. He said the entry point had been addressed and the attacker had remained detectable for weeks, until approximately a week and a half to two weeks before the interview. He did not identify the access method or confirm encryption.

Operational significance

The initial disruption affected city computer systems and services. KNWA/KFTA reported Aug. 17 that card readers at city offices and the landfill Scale House were unavailable, requiring cash or checks.

The city reported Sept. 15 that payment systems at City Hall, District Court and the landfill had returned and all public-facing city services were online. Its Sept. 16 utility-payment reminder said third-party online utility-payment systems had not been affected.

Public-facing restoration was not complete internal recovery. In the Sept. 24 interview, Dingman said some employees still could not access files previously stored on shared network drives. This establishes continuing internal file-access disruption.

The city said 911 dispatch and emergency response remained functional. No reviewed source establishes interruption to emergency response, water or wastewater operations or transit. Alleged theft of information about those services does not establish an operational outage.

A Sept. 16 Southwest Times Record report, available through AOL, documented a partial network interruption affecting Wi-Fi and meeting livestreaming at the Blue Lion. City Communications Director Josh Buchfink said the event also made some Freedom of Information Act responses difficult. The report placed City Hall card-payment restoration by Aug. 26 and landfill card-payment restoration Sept. 11; neither milestone established full internal recovery.

Disclosure posture

The Aug. 16 announcement supplied the earliest identified public cyber-specific characterization and operational disclosure. Subsequent statements established unauthorized access, exfiltration, publication and a ransom demand. The city said disclosure remained limited while investigation, data review and security work continued.

Current status

As of Nov. 16, material operational disruption is assessed as presumed resolved. Public-facing services had returned, and the Oct. 26 police statement remains the latest dated evidence of an internal restriction. The earlier forecast of recovery within a few weeks no longer establishes a defensible expectation of continuing disruption. Full internal restoration and its date remain unconfirmed.

Employee shared-file access remained restricted Sept. 24. The city’s Oct. 8 response said recovery and investigation continued without a final technical restoration date. It also acknowledged a purported copied-data posting, but did not know whether information was being sold. The city reiterated that no ransom or intermediary payment was made. It retained Mullen Coughlin for breach-notification compliance and activated cyber insurance, without disclosing costs or coverage amounts. Review of affected information continued. In an Oct. 17 message reproduced by Talk Business & Politics, City Administrator Jeff Dingman said precautionary letters would go to current employees and covered dependents, offering 24 months of credit monitoring and identity restoration. The city was still reviewing potentially affected information, including HR-related records. That planned recipient group is not a confirmed affected-person count. Two employees told the outlet of suspected misuse of their Social Security numbers for tax returns; the city had not established a causal connection to the breach. Neither those reports nor the protective services verify the attacker’s claimed data categories.

In an Oct. 23 KUAF interview, Talk Business & Politics reporter Michael Tilley said key systems remained unrestored and the Police Department was still struggling without a computer system. This attributed account documents continuing internal disruption; it does not establish a loss of emergency response, an outage of every police application or continued attacker access.

In an Oct. 28 report on campaign-sign thefts, police spokesperson Aric Mitchell said in an Oct. 26 email that the cyberattack still prevented broad searches for reported incidents without specific dates, times and addresses. His estimate that computer services might return within a few weeks was a forecast, not a restoration announcement.

Confidence and uncertainty

Confidence is high in unauthorized access, data theft and publication, a ransom demand, payment denial and continuing internal file-access disruption because the city or its named administrator confirmed them.

An Interlock claim recorded by ransomware.live names the city and its domain. The previously captured Interlock-branded page alleged 5,720 GB, millions of files, law-enforcement records, Social Security numbers, mobile-device records, water-system information and 911 data. These categories and quantities remain claims, not authenticated findings. Dingman did not confirm the group’s roughly 5.7-terabyte figure and described a possible one-to-two-terabyte amount as an uncertain impression. Neither estimate is treated as a verified total.

Interlock attribution and ransomware involvement remain low-confidence assessments. Confirmation of theft and a ransom demand does not establish the attacker’s identity or encryption. A subscriber-limited expert report’s accessible introduction distinguishes possession of data from responsibility for the intrusion; its inaccessible reasoning was not used to upgrade attribution.

Analytic gaps

Unresolved issues include the exact access vector, malware or encryption, complete affected-system inventory, verified data volume and categories, affected-person count, notification findings, attacker identity and full technical recovery date. The claimed data set has not been independently authenticated.

Threat actor and claim

Listed as: City of Fort Smith ArkansasSource: ransomware.liveDiscovered:

Claim details

Interlock’s branded leak page names the City of Fort Smith and fortsmithar.gov and claims a 5,720 GB collection containing 4,882,956 files and 326,671 folders. It alleges law-enforcement data, more than 100,000 Social Security numbers, police records, mobile-device records, water-system information and 911 call data. The screenshot documents the claim but does not establish the files’ authenticity or provenance. The city subsequently confirmed data theft and publication and a ransom demand, but has not confirmed encryption or Interlock’s involvement. The claimed categories, quantities and provenance remain unverified.

Organizations involved

Impacted location

Sources

Network security event disrupts Fort Smith, Arkansas, city services

We reported that a network security event disrupted certain city computer systems and services; 911 dispatch and emergency response remained fully functional, and no full restoration had been announced by Monday morning.

City of Fort Smith Responding to Network Security Event

The city said a security event affected its computer network and disrupted certain computer systems and city services. It said 911 dispatch and emergency-services response remained fully functional while restoration work continued with government partners, federal law enforcement and cybersecurity specialists.

Latest News | Fort Smith experiencing 'network security' issue

The outlet reported that the City of Fort Smith had identified a security event affecting its computer network on Sunday, Aug. 16.

Fort Smith services down due to “network security event,” city says

KNWA/KFTA reported that Fort Smith still had network issues Aug. 17. Card readers at city offices and the landfill Scale House were offline, requiring cash or checks, while the city said updates would follow when systems returned online.

City Administrator Jeff Dingman Provides Update on Cybersecurity Event

Primary release confirms unauthorized entry through police department, exfiltration, restored public-facing services and continuing additional-system restoration.

Reminder: Online Utility Bill Payment Available to Residents

Third-party online utility-payment systems were not affected; distinguishes them from city-office card readers.

Fort Smith security event: Why silence can help, also hurt

City communications director Josh Buchfink said the event made some FOIA responses difficult. The report described Blue Lion Wi-Fi/livestream interruption and placed City Hall card-payment restoration by Aug.26 and landfill restoration Sept.11; these did not establish full internal recovery.

Fort Smith to help employees with credit monitoring, ID restoration

Reproduces Oct.17 city administrator memo announcing precautionary letters and24months of credit monitoring/identity restoration for current employees and covered dependents. Data review continues; reported employee tax-related SSN misuse has no established causal link to breach.

Fort Smith eyes Cisterna Park plans as cyberattack fallout grows

In an Oct.23 interview, reporter Michael Tilley said key city systems remained unrestored and the Police Department was still struggling without a computer system. This is an attributed account of internal disruption, not evidence of failed emergency response or a verified breached-person count.

Fort Smith mayoral candidates say theft of campaign signs is issue

Police spokesperson Aric Mitchell said in an Oct.26 email that the cyberattack made broad report searches difficult without specific dates, times and addresses; restoration in a few weeks remained a hope.

Information & Technology

The city says its information technology department supports municipal telecommunications, servers, computers, software, network, website, intranet and e-government services.

City of Fort Smith official website

The organization’s official website describes its identity, services, operating role and public or customer-facing programs.

Gazetteer Files

The Census Bureau Gazetteer Files provide authoritative geographic reference data for states, counties, county equivalents and places in the United States.

Fort Smith resident service page

As reviewed Aug. 31, the city service page directed residents to ordinary online and telephone channels for water, sewer and solid-waste service and did not identify a continuing cyber-related payment restriction or workaround.

See something that needs correction?

Signed-in members can report an error, update, or missing source.