Windows Driver File MoriyaStreamWatchmen.sys Created in System32\drivers

Alerts when the Windows system32 drivers directory receives the MoriyaStreamWatchmen.sys file.

FreeReviewedSigma · Critical · v5
Product
windows
Category
file_event
Author
Bhabesh Raj (SigmaHQ), DRL 1.1
Published
2021-05-06
Updated
2026-07-31

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule triggers when the file event creates or writes a specific driver filename, MoriyaStreamWatchmen.sys, at C:\Windows\System32\drivers. Creating a kernel driver in this location is a common persistence and privilege-escalation technique because it can load with system privileges. The detection relies on Windows file event telemetry that records the target file path and name for newly created driver files.

Related detections9 linkedT1543.003 — drag to rearrange
Suspicious Service DLL Hijack of IKEEXT or PrintNotify
Service Hiding via SC Sdset Security Descriptor Modification
Malicious Service DLL Hijack for Persistence via Lotus Blossom
Malicious TinyTurla ServiceDll Registration via svchost Group (via registry_set)
Suspicious ToyMaker LAGTOY Service Creation Masquerading as WmiPrvSV via sc.exe
Malicious Service Creation With Autostart binPath via sc.exe (via process_creation)
Malicious svchost Service Creation for TinyTurla Persistence (via process_creation)
Malicious Service Creation Masquerading as nslookup (via process_creation)
Interactive Service Creation Executing cmd via sc.exe
Windows Driver File MoriyaStreamWatchmen.sys Created in System32\drivers
Pivot detection · T1543.003 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.