huntrule

Suspicious File Creation by OpenEDR ITSMService on Windows

Alerts on Windows file creations by OpenEDR ITSMService.exe when the target ends with common executable or script/archive extensions.

FreeReviewedSigma · Medium · v2
Product
windows
Category
file_event
Author
@kostastsale (SigmaHQ), DRL 1.1
Published
2026-02-19
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Lateral Movement → C2

  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 file creation events where OpenEDR's ITSMService.exe creates files with potentially dangerous extensions. Attackers could leverage remote management functionality to stage or deploy executable and script content on endpoints. Telemetry relies on Windows file event logging that records the creating process image and the target filename extension.

Reporting behind it

Related detections9 linkedT1105 — drag to rearrange
Suspicious Velociraptor Agent Deployment via msiexec From Cloud Storage
BITS Payload Downloaded via Commandline (via process_creation)
BITS Payload Downloaded via PowerShell (via powershell)
Suspicious node.exe or code.exe Execution from Public Music Directory
Windows: TacticalRMM Agent Installed with API/Auth Flags Pointing to Remote RMM Server
Suspicious Remote Script Transfer via Bitsadmin (via process_creation)
Suspicious PowerShell Download Cradle via ClickFix Fake CAPTCHA (via process_creation)
Malicious Curl MSI Download to ProgramData via Process Creation
Suspicious CloudZ RAT Payload Download via curl to ProgramData
Suspicious File Creation by OpenEDR ITSMService on Windows
Pivot detection · T1105 · 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.