Windows: Process Execution of Suspicious hxtsr.exe (Outside WindowsApps)

Alerts when hxtsr.exe runs from a non-expected WindowsApps Microsoft.WindowsCommunicationsApps location.

FreeReviewedSigma · Medium · v2
Product
windows
Category
process_creation
Author
Sreeman (SigmaHQ), DRL 1.1
Published
2020-04-17
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags process executions where the image path ends with \hxtsr.exe, but the executable is not found in the expected WindowsApps Microsoft.WindowsCommunicationsApps subfolder. Attackers may use a filename masquerade to appear legitimate by planting or executing a fake hxtsr.exe elsewhere on the system. The detection relies on process creation telemetry including the full Image path and uses string matching on the executable name and location.

Related detections9 linkedT1036 — drag to rearrange
Suspicious Rclone Exfiltration Masquerading as wininit.exe
Suspicious Executable Running from Public Pictures Directory
Suspicious Python Execution via Renamed Synaptics Binary
Agent Tesla Persistence via Realtek Named Scheduled Task Batch
Suspicious Interlock Fake Updater Executable Execution
Malicious User Account Created by a Computer Account (via security)
Suspicious Execution of agent.exe From WinSyncDefender AppData Directory (via process_creation)
Malicious Scheduled Task Masquerading as Auto Update via schtasks (via process_creation)
Suspicious Novaservice Binary Executing From Public User Directory (via process_creation)
Windows: Process Execution of Suspicious hxtsr.exe (Outside WindowsApps)
Pivot detection · T1036 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.