Detection: Windows Suspicious Named Pipe

Updated Date: 2026-05-13 ID: 3a76d52f-a007-4a65-a37d-f313c2c83f31 Author: Raven Tait, Splunk Type: TTP Product: Splunk Enterprise Security

Description

The following analytic detects the creation or connection to known suspicious named pipes. It leverages Sysmon EventCodes 17 and 18 to identify known default pipe names used by malicious or suspicious tools. If confirmed malicious, this could allow an attacker to abuse these to potentially gain privilege escalation, persistence, c2 communications, or further system compromise.

Search

 1`sysmon`
 2EventCode IN (17, 18)
 3NOT process_path IN (
 4    "*:\\Program Files \(x86\)\\Adobe*",
 5    "*:\\Program Files \(x86\)\\Google*",
 6    "*:\\Program Files \(x86\)\\Microsoft*",
 7    "*:\\Program Files\\Adobe*",
 8    "*:\\Program Files\\Google*",
 9    "*:\\Program Files\\Microsoft*",
10    "*:\\Windows\\system32\\SearchIndexer.exe",
11    "*:\\Windows\\System32\\svchost.exe",
12    "*:\\Windows\\SystemApps\\Microsoft*",
13    "*\\Amazon\\SSM\\Instance*",
14    "*\\AppData\\Local\\Google*",
15    "*\\AppData\\Local\\Kingsoft\\*",
16    "*\\AppData\\Local\\Microsoft*",
17    "System",
18)
19
20
21| stats min(_time) as firstTime max(_time) as lastTime
22  count by dest dvc process_exec process_guid process_id process_path
23           pipe_name user_id process_name signature signature_id vendor_product
24
25
26| lookup suspicious_named_pipes suspicious_pipe_name AS pipe_name OUTPUT tool, type, description
27
28| where isnotnull(tool)
29
30| `security_content_ctime(firstTime)`
31
32| `security_content_ctime(lastTime)`
33
34| `windows_suspicious_named_pipe_filter`

Data Source

Name	Platform	Sourcetype	Source
Sysmon EventID 18	Windows	`'XmlWinEventLog'`	`'XmlWinEventLog:Microsoft-Windows-Sysmon/Operational'`
Sysmon EventID 17	Windows	`'XmlWinEventLog'`	`'XmlWinEventLog:Microsoft-Windows-Sysmon/Operational'`

Macros Used

Name	Value
sysmon	`(source=WinEventLog:Microsoft-Windows-Sysmon/Operational OR source=XmlWinEventLog:Microsoft-Windows-Sysmon/Operational OR source=Syslog:Linux-Sysmon/Operational)`
windows_suspicious_named_pipe_filter	`search *`

windows_suspicious_named_pipe_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK

+ Kill Chain Phases

+ NIST

+ CIS

- Threat Actors

ID	Technique	Tactic
T1021.002	SMB/Windows Admin Shares	Lateral Movement
T1055	Process Injection	Privilege Escalation
T1559	Inter-Process Communication	Stealth

Exploitation

Installation

DE.CM

CIS 10

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting	Value
Disabled	true
Cron Schedule	`0 * * * *`
Earliest Time	`-70m@m`
Latest Time	`-10m@m`
Schedule Window	`auto`
Creates Finding (Notable)	Yes
Rule Title	`%name%`
Rule Description	`%description%`
Notable Event Fields	user, dest
Creates Intermediate Finding (Risk Event)	No

TTP detections generate a Finding (Notable) and may generate Intermediate Findings (Risk Events) for associated entities.

Implementation

To successfully implement this search, you need to be ingesting logs with the process name and pipename from your endpoints. If you are using Sysmon, you must have at least version 6.0.4 of the Sysmon TA.

Known False Positives

False positives should be rare, investigate matches and apply additional filters as needed.

Associated Analytic Story

Finding

Title	Entity Field	Entity Type	Risk Score
An instance of $process_name$ located in $process_path$ was identified on endpoint $dest$ accessing known suspicious named pipe $pipe_name$.	dest	system	50

Threat Objects

Field	Type
process_name	process_name

References

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	✅ Passing	N/A	N/A	N/A
Unit	✅ Passing	Dataset	`XmlWinEventLog:Microsoft-Windows-Sysmon/Operational`	`XmlWinEventLog`
Integration	✅ Passing	Dataset	`XmlWinEventLog:Microsoft-Windows-Sysmon/Operational`	`XmlWinEventLog`

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

Source: GitHub | Version: 5