Windows Named Pipe Creation Matching Suspected Turla Pipe Names

Alert on Windows named pipe creation when the PipeName matches Turla-associated strings.

FreeReviewedSigma · Critical · v5
Product
windows
Category
pipe_created
Author
Markus Neis (SigmaHQ), DRL 1.1
Published
2017-11-06
Updated
2026-07-31

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Windows named pipe creation events where the pipe name matches a small set of specific strings associated with Turla group samples. Attackers can use named pipes for local inter-process communication and to stage or proxy payload components, making unusual pipe creation a useful indicator. It relies on telemetry from Windows named pipe events (e.g., Sysmon pipe creation events) that expose the created PipeName value.

Related detections9 linkedT1106 — drag to rearrange
Nullsoft Scriptable Installer Script (NSIS) execution
Nullsoft Scriptable Installer Script (NSIS) file creation
Windows PowerShell ScriptBlock keyword match for WinPwn tool usage
Windows process command line matches WinPwn tool execution keywords
PowerShell Scripts Calling WinAPI DLLs on Windows
Windows PowerShell ScriptBlock WinAPI Function Calls
Windows Process Creation: WinAPI Function Names in Command-Line
Linux auditd: BPFDoor .pid or .lock file access in /var/run
Windows HandleKatz: Duplicate LSASS Handle via Process Access with Handle Duplication Rights
Windows Named Pipe Creation Matching Suspected Turla Pipe Names
Pivot detection · T1106 · 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.