Windows Suspicious Named Pipe
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…
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.
Detection logic
Detection requirements
- Platform
- LinuxmacOSWindows
The rule states no platform. This is derived from the 3 ATT&CK techniques it maps to.
- Log source category
- sysmon_eventid_17sysmon_eventid_18
Known benign triggers
- False positives should be rare, investigate matches and apply additional filters as needed.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| attack.mitre.org/techniques/T1218/009/ | 10 |
| docs.microsoft.com/en-us/windows/win32/ipc/named-pipes | 4 |
From the source
- At source
- Open at source
- Upstream identifier
- 3a76d52f-a007-4a65-a37d-f313c2c83f31
- Tagged by the source as
- APT37 Rustonotto and FadeStealerBlackByte RansomwareBrute Ratel C4Cobalt StrikeDarkSide RansomwareGozi MalwareGraceful Wipe Out AttackHellcat RansomwareLockBit RansomwareMeterpreterRemote Monitoring and Management SoftwareTrickbotTuoniEndpointendpointSplunk CloudSplunk EnterpriseSplunk Enterprise Securityendpoint
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Oct 6, 2026
- Version
- 2