Threat reportRansomwareTL-2026-1948

City of Coweta, Oklahoma Hit by Anubis Ransomware Attack

highACTIVE

City of Coweta, Oklahoma Hit by Anubis Ransomware Attack (TL-2026-1948) is a high-severity ransomware operation, first published 2026-08-09. It is attributed to Anubis with medium confidence, affects City of Coweta, Oklahoma Municipal IT systems (City Hall network, maps to 14 MITRE ATT&CK techniques (T1005, T1059, T1078), and is covered by 9 detection rules and 10 indicators of compromise.

Severity
HIGHAssessed severity
CVEs
0None referenced
Techniques
14MITRE ATT&CK
Actors
1Anubis
Detection rules
9SPL · KQL · Sigma
IOCs
10Indicators of compromise

Key facts for TL-2026-1948

Threat ID
TL-2026-1948
Severity
HIGH
Status
ACTIVE
Category
RANSOMWARE
First published
Last reviewed
Attribution
Anubis
Attribution confidence
MEDIUM
Motivation
FINANCIAL
Target sectors
government administration
Target regions
North America
Detection rules
9
Indicators of compromise
10

Malware and tooling in City of Coweta, Oklahoma Hit by Anubis Ransomware Attack

Malware and tooling: Anubis Ransomware, anubis, cloudflared, github.com/ecies/go

How City of Coweta, Oklahoma Hit by Anubis Ransomware Attack works

On Wednesday, August 5, 2026, the City of Coweta, Oklahoma suffered a system-wide ransomware attack that encrypted city computer systems and files, taking most municipal services offline. One local outlet (KTUL) attributes the intrusion to the Anubis Ransomware-as-a-Service operation; the city refused to negotiate or pay and is restoring from an offsite backup.

On Wednesday, August 5, 2026, the City of Coweta, Oklahoma suffered a system-wide ransomware attack that encrypted local files, Word documents, Excel spreadsheets, and municipal financial systems across City Hall, taking most computer-based city services offline. The City's own website and its third-party online billing portal (Xpress Bill Pay) were unaffected because they are hosted off-site, and the Coweta Police and Fire Departments continued normal operations, including 911 dispatch, because they run on separate off-site systems (e.g., LexisNexis) that were not touched. Credit card and other payment data were not stored on City servers and were confirmed not accessed. The City immediately engaged its contracted IT provider and additional third-party cybersecurity professionals, placed protective holds on municipal bank accounts, reset usernames and passwords, and reported the incident to local and state authorities with federal (FBI) reporting in process. City Manager Julie Casteen publicly confirmed the attackers demanded a ransom but that the City refused to open any line of communication with them, citing her own past experience at another municipality where paying a ransom failed to resolve the intrusion. The City confirmed it holds an offsite backup and targeted the Monday after disclosure (2026-08-10) to begin restoring systems once they are cleared of the ransomware, and separately announced plans to upgrade authentication from multi-factor authentication (MFA) to passkeys.

Only one of the outlets that broke the story, KTUL, names the ransomware strain as 'Anubis'; the DataBreaches.net, Fox23, KJRH, and NewsOn6 write-ups of the same incident do not disclose a group/strain name, and none of the five articles reviewed publish a ransom note, extension, hash, or other technical artifact tying the intrusion to a specific family. Attribution here is therefore held at MEDIUM confidence, corroborated only by KTUL's single sourcing (echoed verbatim in a Fox23 sister-outlet republish) rather than independent forensic confirmation from the City, FBI, or a named incident-response firm. Notably, open-source reporting on the Anubis operation states its operators have publicly claimed to exclude government, education, and non-profit targets from their program rules — a policy commonly violated by RaaS affiliates in practice (mirroring similar unenforced 'no hospitals/no government' pledges by groups like Conti and LockBit), but a discrepancy worth flagging rather than silently resolving.

Anubis is a Ransomware-as-a-Service (RaaS) operation first observed publicly in December 2024, evolved from an earlier prototype tracked as 'Sphinx.' Affiliates most commonly gain initial access via spear-phishing emails carrying malicious attachments or links impersonating trusted senders, and separately via abuse of exposed internet-facing remote-access services — particularly RDP — using compromised, brute-forced, or previously obtained credentials. As of mid-2026, security researchers (TechTimes, Red Secure Tech, Techzine) documented Anubis affiliates also exploiting CVE-2025-5777 ('CitrixBleed 2', a Citrix NetScaler ADC/Gateway session-token disclosure flaw) to bypass MFA and gain initial footholds at scale, and using RMM tools and the Cloudflare Tunnel client ('cloudflared') for stealthy remote access/tunneling during intrusions. None of the Coweta-specific reporting discloses which of these vectors, if any, was used against the City — the CitrixBleed 2 and cloudflared details below describe the actor's documented 2026 playbook generally, not a confirmed technical finding for this incident. Once deployed, the Anubis binary (Go-language) supports command-line flags (`/KEY=`, `/elevated`, `/PATH=`, `/PFAD=`, `/WIPEMODE`) controlling encryption scope and an optional destructive wipe mode; it checks for administrative privileges via raw disk-handle access to `\\.\PHYSICALDRIVE0` and can clone an elevated token via `CreateProcessWithTokenW`, enumerates and excludes core OS/application directories before encrypting eligible files with an Elliptic Curve Integrated Encryption Scheme (ECIES) implementation drawn from the public `github.com/ecies/go` library, deletes Volume Shadow Copies (`vssadmin delete shadows /for=norealvolume /all /quiet`), terminates 50+ processes and disables 40+ services spanning SQL Server, backup agents (Veeam, Acronis), and security software (Sophos, Norton), drops a ransom note (`RESTORE FILES.html`) plus branding assets (`icon.ico`, `wall.jpg`) to `C:\ProgramData`, and appends a `.anubis` extension to encrypted files. Anubis's wipe mode is notable industry-wide for permanently overwriting file contents even where a decryption key is later provided, distinguishing it from encryption-only ransomware. The operation runs a Tor-hosted victim communication/leak-site portal and a double-extortion model, with affiliate revenue splits reported around 80/20 (encryption), 40% to Anubis for data-theft-only engagements, and 50/50 for fully managed extortion.

Remediation at Coweta to date has focused on containment and continuity: engaging outside IT/cybersecurity professionals and (per one outlet) outside cybersecurity attorneys, resetting credentials, safeguarding bank accounts, notifying law enforcement, suspending late fees and water-service disconnections during the outage, accepting in-person check payments as a workaround for disabled card processing at City Hall, and restoring from an offsite backup only after the environment is confirmed clear of the ransomware. The planned MFA-to-passkey migration is a proactive hardening step announced alongside recovery.

MITRE ATT&CK techniques used in TL-2026-1948

Collection

T1005 Data from Local System

Execution

T1059 Command and Scripting Interpreter

Defense Evasion

T1078 Valid Accounts

Credential Access

T1110 Brute Force

defense-impairment

T1112 Modify Registry

Initial Access

T1133 External Remote Services; T1190 Exploit Public-Facing Application; T1566.001 Spearphishing Attachment

Privilege Escalation

T1134.002 Create Process with Token

Impact

T1485 Data Destruction; T1489 Service Stop; T1490 Inhibit System Recovery; T1657 Financial Theft

Command and Control

T1572 Protocol Tunneling

Affected products and versions in City of Coweta, Oklahoma Hit by Anubis Ransomware Attack

  • City of Coweta, Oklahoma — Municipal IT systems (City Hall network, financial/records systems)
    Vulnerable versions: Pre-incident City Hall network configuration (MFA-based authentication)
    Fixed in: Passkey-based authentication upgrade announced, in progress as of 2026-08-08

Remediation for City of Coweta, Oklahoma Hit by Anubis Ransomware Attack

Patches

  • Apply vendor patches for any internet-facing Citrix NetScaler ADC/Gateway appliances (CVE-2025-5777) if present in the environment
  • Ensure Volume Shadow Copy Service and backup agents are protected against administrative-level tampering (vssadmin abuse)

Immediate actions

  • Do not open communication with or pay the ransomware operators
  • Immediately engage a contracted IT provider and third-party incident-response/cybersecurity professionals
  • Reset all usernames and passwords for potentially affected accounts
  • Place protective holds/monitoring on municipal bank accounts
  • Report the incident to local, state, and federal (FBI) law enforcement

Workarounds

  • Accept in-person check payments and defer card processing at City Hall until systems are restored
  • Suspend late fees and water-service disconnections for nonpayment during the outage
  • Continue routing 911/police/fire operations through unaffected off-site systems

Longer-term hardening

  • Restore systems and data only from offsite/immutable backups after full ransomware eradication is confirmed
  • Migrate authentication from multi-factor authentication (MFA) to phishing-resistant passkeys
  • Keep public-safety systems (police, fire, 911/dispatch) on network-segmented, off-site infrastructure isolated from general municipal IT
  • Inventory and monitor internet-facing remote-access services (RDP, VPN/SSL-VPN, Citrix NetScaler ADC/Gateway) for exposure and known exploited vulnerabilities such as CVE-2025-5777 ('CitrixBleed 2')
  • Deploy tamper-resistant EDR and backup-agent protections to prevent termination of security software (e.g., Sophos) and backup services (e.g., Veeam, Acronis) during an active intrusion

Timeline of City of Coweta, Oklahoma Hit by Anubis Ransomware Attack

  • The City places protective safeguards on municipal bank accounts and changes usernames and passwords for affected accounts.
  • The City immediately engages its contracted IT provider and additional third-party cybersecurity professionals to secure systems and prevent further intrusion.
  • A system-wide ransomware attack encrypts City of Coweta, Oklahoma computer systems and files (local files, Word/Excel documents, financial systems), taking most City Hall computer-based services offline.
  • The City reports the incident to local and state authorities; federal reporting to the FBI is in process.
  • The City and local media (DataBreaches.net, KTUL, Fox23, KJRH) publicly disclose the ransomware attack, confirming an offsite backup exists and that police/fire/911 systems are unaffected.
  • The City announces plans to upgrade authentication from multi-factor authentication (MFA) to passkeys as part of its post-incident hardening.
  • The City targets the following Monday (2026-08-10) to begin restoring systems and data from its offsite backup once the environment is confirmed clear of the ransomware.
  • FBI, local police, and contracted IT professionals investigate server logs to determine the scope and origin of the intrusion.
  • City Manager Julie Casteen confirms attackers demanded a ransom and states the City refuses to open communication with or pay the operators; KTUL attributes the intrusion to the 'Anubis' ransomware strain.

Sources cited for City of Coweta, Oklahoma Hit by Anubis Ransomware Attack

Detection coverage for TL-2026-1948

As of 2026-08-09, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1948 across Splunk SPL, Microsoft KQL and Sigma, covering 10 indicator(s) of compromise. The whole corpus is readable without an account; a free account unlocks full detection query text in Splunk SPL, Microsoft KQL and Sigma; paid tiers add raw indicator values, correlation and the MCP server. Threadlinqs MCP server · View plans.

9 detection rules (Splunk SPL, Microsoft KQL, Sigma) · Blue and above. Compare plans
10 indicators of compromise · Red and above. Compare plans

Threadlinqs Intelligence — Real-Time Threat Detection Platform

[ 0 threats ] [ 0 det ] [ CRIT: 0 ] [ HIGH: 0 ]
// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level
Fig. 01 · Threat weatherIndexing the archive…
1 square = 1 threat · click to open

Latest Threats