Windows Named Pipe Creation for Known Credential Dumping Tool Pipe Names

Alerts on Windows named pipe creations matching credential dumping tool pipe names.

FreeReviewedSigma · Critical · v2
Product
windows
Category
pipe_created
Author
Teymur Kheirkhabarov, oscd.community (SigmaHQ), DRL 1.1
Published
2019-11-01
Updated
2026-07-31

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies Windows named pipe creation events where the pipe name contains specific strings associated with well-known credential dumping tools. Attackers may use named pipes to transfer data or coordinate execution during credential access, making these pipe names valuable indicators of malicious activity. It relies on telemetry from Windows pipe creation logging (e.g., Sysmon named pipe events) capturing the created pipe name.

Related detections9 linkedT1003.002 — drag to rearrange
Windows Credential Dump Tool Artifacts Written to Disk via File Events
Windows Process Creation: Detect Mimikatz Tool and Module Command-Line Usage
Windows System Service Execution of Credential Dumping Tools (Service Control Manager Event 7045)
Windows Security EID 4697 Service Execution of Credential Dumping Tools
Windows PUA: MemProcFS memory dump mounting via -device
Windows reg.exe Registry Hive Dumping for SAM, SYSTEM, and SECURITY
Windows Event Logs: Mimikatz Keyword Indicators
Malicious Mimikatz Credential Access Module Invocation
Zeek SMB: Network Share File Transfers of Credential-Related Filenames
Windows Named Pipe Creation for Known Credential Dumping Tool Pipe Names
Pivot detection · T1003.002 · 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.