Windows RMM Named Pipe
The following analytic detects the creation or connection to known suspicious named pipes, which is a technique often used by offensive tools. It leverages Sysmon EventCodes 17 and 18 to identify known default pipe…
Description
The following analytic detects the creation or connection to known suspicious named pipes, which is a technique often used by offensive tools. It leverages Sysmon EventCodes 17 and 18 to identify known default pipe names used by RMM tools. If confirmed malicious, this could allow an attacker to abuse these to potentially gain persistence, command and control, 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
- Some false positives may occur from RMM software used in your environment. Apply filters based on known legitimate RMM software in your environment to reduce false positives.
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
- c07c7138-edf5-4a16-8b24-3842599235bf
- Tagged by the source as
- Cactus RansomwareCISA AA24-241ACommand And ControlGhostRedirector IIS Module and Rungan BackdoorGozi MalwareInsider ThreatInterlock RansomwareRansomwareRemote Monitoring and Management SoftwareScattered Lapsus$ HuntersScattered SpiderSeashell BlizzardEndpointendpointSplunk 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