Zeek SMB spoolss Named Pipe (IPC$) Access

Flags Zeek SMB events accessing the spoolss named pipe via IPC$.

FreeReviewedSigma · Medium · v2
Product
zeek
Service
smb_files
Author
OTR (Open Threat Research), @neu5ron (SigmaHQ), DRL 1.1
Published
2018-11-28
Updated
2026-07-31

ATT&CK techniques

Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags SMB file activity where the name field is "spoolss" and the path ends with "IPC$", indicating attempts to access the spoolss named pipe over the SMB IPC share. Attackers can use this to provoke network authentication from systems that expose the spool service, which can facilitate lateral movement or follow-on abuse. It relies on Zeek SMB file logs capturing both the IPC$-scoped path and the spoolss pipe name.

Related detections9 linkedT1021.002 — drag to rearrange
Suspicious Impacket Style Command Execution with ADMIN Share Output Redirect
Suspicious Active Directory Reconnaissance via In-Memory Offensive PowerShell (via ps_script)
Suspicious NetExec Post-Exploitation Tool Execution via nxc (via process_creation)
Suspicious SMB Admin Share Mapping for Lateral Tool Transfer (via process_creation)
Suspicious Impacket Remote Execution Tool Usage via process_creation
Suspicious Remote Service Execution via PsExec (via process_creation)
Suspicious RemCom Service Named Pipe for Lateral Movement (via pipe_created)
Suspicious WMIC Remote Process Creation for Lateral Movement
Suspicious File Copy to Administrative SMB Share via net.exe (via process_creation)
Zeek SMB spoolss Named Pipe (IPC$) Access
Pivot detection · T1021.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.