Cyber & AI intelligence
Briefs indexed3931
Issues37
Published Mondays07:30 CT
▣ Breach FORT-SMITH-AR 2026-11-20

City of Fort Smith: Forensic Report Confirms 25-Day Intrusion Claimed by Interlock Ransomware

"A forensic investigation commissioned for the City of Fort Smith, Arkansas, has found that attackers were inside the city's network from July 24 to August 18, 2026. That is more than three weeks before the city says it…"

A forensic investigation commissioned for the City of Fort Smith, Arkansas, has found that attackers were inside the city's network from July 24 to August 18, 2026. That is more than three weeks before the city says it first spotted the intrusion, and two days after it did. The summary report by PNG Cyber was obtained by Talk Business & Politics and released on November 19. It says the attackers moved through the network, took over privileged accounts, stole data and launched a file encryption attack on August 16. According to Talk Business & Politics, the report also backs up the Interlock ransomware group's claim that it took about 5.72 terabytes of city data. On November 18 the city said for the first time that personal information had been stolen. That includes Social Security numbers, biometric data, medical information and law enforcement records. City Administrator Jeff Dingman says there is no way to tell how many people are affected.

What Happened

The city says it first noticed a "cybersecurity event" on August 16. That same day it hired Mullen Coughlin LLC, a law firm based in Devon, Pennsylvania, as outside counsel for breach notification. The firm then brought in PNG Cyber to investigate. Talk Business & Politics reports that PNG looked at data from the city's Trend Vision One endpoint monitoring tool, three forensic images, and triage data from 872 city computers. It concluded that the attackers "accessed Client's network from July 24, 2026, to August 18, 2026."

The timeline has been confusing, and the city's own account has changed:

Interlock claimed the attack on its leak site. Siberpol, which tracks leak sites, dates the post to September 15. SiberMagazin says the claim appeared in early September. Talk Business & Politics, citing Ransom-DB and DysruptionHub, also reports Interlock as the claimant. The city has not publicly named the group. SiberMagazin notes that the city has not confirmed Interlock's specific claims about what was stolen.

In September, Dingman said the investigation was nearing its end and that "the threat has been contained." Talk Business & Politics points out that the forensic summary came out more than two months after that statement.

What Was Taken

Volume. Interlock claims it took 5,720 GB, about 5.72 TB, of city data. Talk Business & Politics reports that the PNG report confirms that figure. Siberpol gives a slightly lower figure of 5.6 TB from the leak-site post. Talk Business & Politics also reports that "much of that data is lost," meaning the encryption left some of it unrecoverable.

Data types confirmed by the city. The November 18 notice says the stolen data varies by person and may include:

Who may be affected. Dingman told 5NEWS that anyone who gave personal information to the city's public safety services could be affected. That includes people who were pulled over, received a citation or filed an accident report. He said there is no way to determine the total number. Talk Business & Politics, followed by SiberMagazin, identified groups whose data is potentially at risk: 1,032 city employees, more than 36,000 residents and businesses with water and sewer accounts, and current and former city vendors. These are counts of people whose data may be exposed. They are not confirmed victim totals.

What Interlock says it has. According to Talk Business & Politics, Interlock says it took police material including photos, information about the water supply system, and data on systems that support several city departments. Siberpol says the leak-site post also mentions 911 dispatch records. SiberMagazin reports that Interlock claims to hold more than 100,000 Social Security numbers. None of these claims has been confirmed by the city or by any independent source.

Signs of misuse. Arkansas Express, citing Talk Business & Politics, reports that two city employees found someone had used their Social Security numbers to file tax returns and claim refunds from the IRS. Dingman said the attacker had published city data, and that the city used what was released to work out what had been exposed.

Why It Matters

The detection gap. The attackers were inside for about 23 days before anyone noticed, and they had time to get privileged credentials and steal data first. Fort Smith had an endpoint monitoring product in place, and that product later supplied key forensic evidence. Even so, the intrusion was only caught when the encryption started. Having monitoring tools is different from having someone watching the alerts and acting on them.

Shifting public statements. First the city said no personal data was exposed. Then it blamed the police department. Then it reversed both. Months of slow disclosure made public trust worse and fed into local politics: at a mayoral debate, candidate Dan Williams claimed a department head had warned city leaders about a possible cyberattack before the breach and was "basically … laughed at." Candidate Christina Catsavis, who sits on the city's Board of Directors, said she had no knowledge of any such warning and called for "a full public accounting." The warning claim has not been verified.

Law enforcement and biometric data. Stolen Social Security numbers can be partly dealt with through credit freezes and IRS identity protection PINs. Biometric data and police records can't be changed or reissued. If they leak, the people involved, including crime victims, witnesses and informants, can face lasting risks to their privacy and physical safety.

Pressure on local government. Cities hold sensitive data from every service they run, often on shared networks with limited segmentation and small security teams. That combination is attractive to double-extortion groups, which both steal data and encrypt systems.

The Attack Technique

Neither the city nor PNG Cyber has said publicly how the attackers first got in. The PNG summary, as reported by Talk Business & Politics, describes this sequence:

  1. Initial access on July 24, 2026. The method has not been disclosed, and the city now says it was not through police systems.
  2. Lateral movement across the city's networks over the following weeks.
  3. Takeover of privileged user accounts.
  4. Data theft. The city puts this between August 5 and August 15.
  5. File encryption launched on August 16, the same day the city detected the attack.
  6. Continued access until August 18, two days after detection.

This matches the standard double-extortion pattern of stealing data before encrypting it. In past public reporting, including a joint CISA and FBI advisory from 2025, Interlock was described as getting in through fake software update downloads, fake CAPTCHA pages that trick users into running commands themselves, and remote access tools. There is no public evidence on whether any of these methods were used against Fort Smith.

The two days of access after detection are worth noting. They suggest that removing the attackers from the network did not happen immediately once the encryption was spotted.

What Organizations Should Do

  1. Make sure someone is watching the alerts. Endpoint monitoring only helps if someone reviews and acts on alerts quickly. Small governments without a round-the-clock security team should consider a managed detection and response service. Tune alerts for the signs that come before encryption: unusual use of admin accounts, remote execution tools, and large outbound data transfers.
  2. Lock down privileged accounts. Require phishing-resistant MFA for all admin and remote access. Keep separate admin accounts with tiered access. Rotate service account credentials. Alert on new privileged group memberships or unusual logins by privileged accounts.
  3. Separate public safety systems from the rest of the network. Police records, 911 dispatch, water and wastewater control systems, and HR or payroll should not sit on a flat network. Block lateral movement between departments by default.
  4. Monitor and limit outbound data. Multiple terabytes leaving over about 10 days should trigger alerts. Set baselines for normal outbound traffic, block unapproved cloud storage and file transfer tools, and flag large or long-running uploads.
  5. Plan for complete removal of attackers. Response plans should cover resetting credentials across the whole environment, including resetting the Kerberos ticket-signing account twice, and confirming the attacker is gone before announcing the threat is contained.
  6. Tell people early and accurately. Don't rule out personal data exposure before the investigation can support it. Offer affected people credit monitoring, IRS Identity Protection PINs and credit freezes as early as possible. In Fort Smith, fraud against employees was reported before any public notice went out.

Anyone who thinks they may be affected can call the city's toll-free assistance line at 833-931-8400, Monday through Friday, 8 a.m. to 8 p.m. Central Time.

Sources: Report provides info about attack on city of Fort Smith computer sy... | City of Fort Smith reports personal data impacted by August cyberat... | Fort Smith mayoral candidates address cyberattack after city warns... | Fort Smith changes story on computer system attack origin; law firm... | City of Fort Smith Arkansas targeted by Interlock ransomware group | Fort Smith Offers Credit Monitoring to Employees After Computer Sys... | Fort Smith belediyesi Ağustos saldırısında dosyaların indirildiğini... | Fort Smith says personal information leaked in security event - KHBS