CyberKit

Event IDs

Sysmon event 17

PipeEvent (Pipe Created)

Channel: Microsoft-Windows-Sysmon/Operational. Category: Named Pipe.

What it records

Logs the creation of a named pipe, used for interprocess communication.

Why it matters

Many post-exploitation frameworks and C2 implants use named pipes for interprocess or inter-implant communication, so pipe names/paths are a useful IOC surface documented by Sysmon itself.

What triggers it

Legitimate Windows services and applications create named pipes constantly, but distinctive or randomly-named pipes are also a hallmark of malware and offensive-security C2 frameworks.

Fields that carry the answer

Key fields
FieldWhat it tells you
PipeNameThe name of the named pipe created. Distinctive or randomly-generated pipe names are a common C2/post-exploitation-framework fingerprint worth checking against known-malicious pipe name lists.
ImageThe process that created the pipe, which identifies which process is acting as the IPC server endpoint.

In practice

Event 17 shows Image C:\Windows\System32\spoolsv.exe creating PipeName \spoolss, ordinary print-spooler IPC, but a PipeName like \msagent_de5f, with no descriptive purpose, created by Image C:\Users\jsmith\AppData\Local\Temp\beacon.exe is characteristic of a post-exploitation framework opening its named-pipe C2 endpoint, which an analyst would then match against Event 18 to see what second process connects to it.

Sample record

Pipe Created:
RuleName: -
EventType: CreatePipe
UtcTime: 2024-01-15 14:55:30.567
ProcessGuid: {A1B2C3D4-E5F6-4A5B-8C9D-0E1F2A3B0009}
ProcessId: 3300
PipeName: \PSHost.14a2b3c4.1.2.0.0
Image: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
User: CORP\jsmith

Sources

Paste a record into Event XML or open a log in EVTX Reader.