Skip to navigation

Threat reportData BreachTL-2026-1640

Kootenai County, Idaho Ransomware Attack Exposes Resident Personal Information

mediumACTIVE

Kootenai County, Idaho detected a ransomware attack on its computer network on March 30, 2026. Third-party cybersecurity and forensics consultants confirmed cyber criminals extracted personal data before the county began mailing breach-notification letters to residents on July 22, 2026. No ransomware group has publicly claimed the attack and the data types and victim count remain undisclosed.

Key facts

IdentifiersTL-2026-1640
SeverityMEDIUM
Affected productsKootenai County, Idaho County government computer network
Malware3AM ransomware
ToolsBloodHound - S0521, Cobalt Strike, Mimikatz, Smoke Loader
MITRE ATT&CK techniquesT1003 OS Credential Dumping, T1048 Exfiltration Over Alternative Protocol, T1057 Process Discovery, T1070 Indicator Removal, T1078 Valid Accounts, T1082 System Information Discovery, T1083 File and Directory Discovery, T1105 Ingress Tool Transfer, T1133 External Remote Services, T1134 Access Token Manipulation, T1218 System Binary Proxy Execution, T1486 Data Encrypted for Impact and 8 more in the attack flow
MotivationFINANCIAL
Target sectorsgovernment administration, public-sector, local-government
Target regionsNorth America, united states of america, Idaho
Detection rules9 (1 shown free)
Sources9 cited sources

Detection coverage

As of 2026-07-22, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1640 across Splunk SPL, Microsoft KQL and Sigma, covering 15 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Phishing-Derived Office Macro Spawning LOLBin (Mshta/PowerShell) Prior to Persistence

Detects an Office application (winword/excel/outlook) spawning mshta.exe or powershell.exe within a short window, the classic phishing-to-execution pivot (T1566 -> T1218 Mshta / T1574 DLL side-loading) documented as SLTT ransomware sector context, frequently followed by Registry Run-key persistence.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1566, T1218, T1574
  • Data sources: sysmon, windows_security, microsoft_defender_for_endpoint
  • Severity: high
  • Confidence: high

Splunk SPL

index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
| eval ParentImage=lower(ParentImage), Image=lower(Image)
| where (ParentImage LIKE "%winword.exe" OR ParentImage LIKE "%excel.exe" OR ParentImage LIKE "%outlook.exe") AND (Image LIKE "%mshta.exe" OR Image LIKE "%powershell.exe" OR Image LIKE "%rundll32.exe")
| table _time, ComputerName, User, ParentImage, Image, CommandLine
| sort -_time

Microsoft KQL

DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName in~ ("winword.exe", "excel.exe", "outlook.exe")
| where FileName in~ ("mshta.exe", "powershell.exe", "rundll32.exe")
| project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, FileName, ProcessCommandLine

Sigma

title: Office Application Spawning Mshta or PowerShell (Phishing Execution Pivot)
id: 5c1a2e3b-1640-4a11-9c02-a1b2c3d4e602
status: experimental
description: Detects Microsoft Office parent processes launching mshta.exe, powershell.exe, or rundll32.exe, consistent with phishing (T1566) leading to System Binary Proxy Execution (T1218) or Hijack Execution Flow (T1574) in SLTT ransomware sector context.
references:
    - https://www.cisa.gov/news-events/cybersecurity-advisories/aa24-060a
author: Threadlinqs Team
date: 2026-07-23
tags:
    - attack.initial_access
    - attack.execution
    - attack.t1566
    - attack.t1218
    - attack.t1574
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        ParentImage|endswith:
            - '\\winword.exe'
            - '\\excel.exe'
            - '\\outlook.exe'
        Image|endswith:
            - '\\mshta.exe'
            - '\\powershell.exe'
            - '\\rundll32.exe'
    condition: selection
falsepositives:
    - Legitimate macro-driven business automation invoking approved scripts
    - Add-in installers that shell out to PowerShell during setup
level: high

Known false positives:

  • Approved macro-enabled workflow templates that call PowerShell for document automation
  • Enterprise add-in installers shelling out to mshta for legacy config dialogs

Tuning notes: Allow-list known signed macro-automation binaries and specific CommandLine hashes used by IT-approved add-ins; raise severity when the child process further spawns network connections or writes to Startup/Run-key locations within 5 minutes.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Valid Account Logon From External-Remote-Service Followed by Registry Run-Key Persistence · unlock with TL Creds
  • Suspected LSASS Credential Dumping via comsvcs.dll MiniDump Preceded by UAC Bypass Marker · unlock with TL Creds
  • Windows Security/System Event Log Cleared Shortly After Elevated Session (Anti-Forensic Log Tampering) · unlock with TL Creds
  • Non-Standard User Registering New Firewall-Disable or Defense-Impairing Command · unlock with TL Creds
  • Bulk Archive Utility Invocation Against User/PII Data Directories Outside Backup Schedule · unlock with TL Creds
  • Shadow Copy / Backup Catalog Deletion Immediately Preceding Mass File-Extension Change (Ransomware Impact) · unlock with TL Creds
  • External Remote Services Brute-Force / Anomalous RDP Logon Success (SLTT Ransomware Initial Access) · unlock with TL Creds
  • Outbound Beacon to Non-Standard Port Immediately Following Archive Creation (Exfiltration Over Alternative Protocol) · unlock with TL Creds

Indicators of compromise

As of 2026-07-22, Threadlinqs Intelligence tracks 15 indicators of compromise for TL-2026-1640.

15 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

On March 30, 2026, Kootenai County, Idaho detected a ransomware intrusion on its government computer network. The county states it immediately secured the network, restored operations, notified federal law enforcement, and engaged nationally recognized third-party cybersecurity and digital-forensics consultants to investigate. County commissioners discussed the incident in a closed executive session on May 19, 2026, and the forensic review determined by late June 2026 that cyber criminals had extracted certain data constituting an 'unauthorized acquisition of personal information' under Idaho Code § 28-51-105. Idaho's breach-notification statute requires government agencies to notify the state Attorney General's office within 24 hours of discovery, one of the shortest mandatory reporting windows in the United States. Beginning July 22, 2026, the county started mailing written notification letters to affected residents and is offering free credit monitoring to eligible victims; residents without on-file contact information can find notice details on the county website. As of the notification date no ransomware group had publicly claimed responsibility on a leak site, and the county has not disclosed the initial access vector, the specific categories of exposed data, or the number of affected individuals. The incident is one of several ransomware-driven data breaches confirmed at Idaho county and municipal governments in the 2025-2026 timeframe (including Gooding County, Twin Falls County, Nampa, Jerome City/County, and Jefferson County), consistent with the broader nationwide pattern of ransomware-as-a-service (RaaS) affiliates and initial-access brokers targeting under-resourced state, local, tribal, and territorial (SLTT) government networks for double-extortion data theft. CISA/FBI/MS-ISAC joint advisories on SLTT-focused ransomware families (e.g., Phobos, AA24-060A) document a common kill chain of RDP brute-forcing or phishing for initial access, credential dumping, discovery, archival staging, exfiltration over alternative protocols, and encryption for impact; that documented pattern is included here as sector/technique context only and is NOT a confirmed attribution for the Kootenai County intrusion, which remains unclaimed and unattributed. This record should be distinguished from the unrelated 2024 Kootenai Health (medical center) ransomware breach attributed to the 3AM ransomware gang, which affected roughly 464,000 patients and involved a different victim organization and a different Idaho county-region entity.

MITRE ATT&CK techniques by tactic:

Credential Access

T1003 OS Credential Dumping

Exfiltration

T1048 Exfiltration Over Alternative Protocol

Discovery

T1057 Process Discovery; T1082 System Information Discovery; T1083 File and Directory Discovery

Defense Evasion

T1070 Indicator Removal

Initial Access

T1078 Valid Accounts; T1133 External Remote Services; T1566 Phishing

Command and Control

T1105 Ingress Tool Transfer

Privilege Escalation

T1134 Access Token Manipulation; T1546 Event Triggered Execution

stealth

T1218 System Binary Proxy Execution

Impact

T1486 Data Encrypted for Impact; T1490 Inhibit System Recovery

Persistence

T1547 Boot or Logon Autostart Execution

privilege-escalation

T1548 Abuse Elevation Control Mechanism

Collection

T1560 Archive Collected Data

Execution

T1574 Hijack Execution Flow

defense-impairment

T1685 Disable or Modify Tools

Remediation

Patches

  • No specific CVE or vulnerable product has been publicly disclosed for this incident; apply standard OS/RDP/VPN patching cadence pending forensic disclosure

Immediate actions

  • Complete resident breach-notification mailing and website notice per Idaho Code § 28-51-105
  • Offer and enroll eligible affected residents in free credit monitoring and identity-theft protection
  • Confirm eradication of attacker persistence mechanisms and rotate all privileged and service-account credentials network-wide
  • Verify Idaho Attorney General and federal law enforcement notification records are complete

Workarounds

  • Restrict or disable exposed RDP; require VPN + MFA for any remote administrative access
  • Enforce account lockout/rate limiting on all internet-facing authentication services to blunt brute-force initial access

Longer-term hardening

  • Deploy EDR/XDR with behavioral ransomware and credential-dumping detection across county endpoints and servers
  • Segment county government network zones (finance, elections, public safety, general administration) to limit lateral movement blast radius
  • Implement centralized, tamper-resistant logging (forward Windows Event Logs off-host) to defeat log-clearing anti-forensics
  • Adopt phishing-resistant MFA for all remote access and privileged accounts
  • Establish immutable, tested offline backups and a documented ransomware incident-response/tabletop program

Affected and fixed versions

  • Kootenai County, Idaho — County government computer network
    Vulnerable versions: Not disclosed
    Fixed in: Not applicable - no vendor patch identified

Timeline

  • County notifies federal law enforcement of the intrusion, per county public statement.
  • Kootenai County detects a ransomware attack on its government computer network and immediately begins securing and restoring operations.
  • Idaho Code § 28-51-105 requires government agencies to notify the Idaho Attorney General's office within 24 hours of discovering a breach of computerized personal information.
  • Kootenai County commissioners discuss the breach in a closed executive session.
  • Third-party cybersecurity and digital-forensics investigation concludes that cyber criminals extracted data constituting an unauthorized acquisition of personal information under Idaho law; some local reporting places the finalized scope determination as late as July 2, 2026.
  • Local outlet PrismNews first publicly reports the breach determination and executive-session discussion, nearly a month ahead of the county's formal resident notification mailing.
  • As of the notification date, no ransomware group has publicly claimed responsibility for the attack on a leak site or elsewhere; data categories and victim count remain undisclosed.
  • Kootenai County begins mailing written breach-notification letters to affected residents and posts notice on the county website; free credit monitoring offered to eligible victims.

Sources cited

Previous and next in data breach

Drafted by the Threadlinqs research pipeline from 9 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats