Sysmon event 18
PipeEvent (Pipe Connected)
Channel: Microsoft-Windows-Sysmon/Operational. Category: Named Pipe.
What it records
Logs when a client connects to an existing named-pipe server.
Why it matters
Correlated with the Pipe Created event, it shows which process actually communicated over a suspicious pipe, helping confirm inter-process C2 or lateral tool-handoff activity.
What triggers it
Normal service-to-service IPC, and in malicious cases, a second-stage payload or beacon connecting to a named pipe set up by an initial implant.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| PipeName | The name of the pipe connected to. Correlate with the matching Event 17 to confirm which server pipe this client reached. |
| Image | The process that connected to the pipe, correlating this with Event 17's Image shows exactly which two processes talked to each other, useful for confirming inter-implant or lateral-tool-handoff activity. |
In practice
Event 18 shows Image C:\Windows\System32\spoolsv.exe as the client connecting to PipeName \spoolss (routine local print-spooler IPC), but a different process, e.g. C:\Windows\Temp\stager.exe, connecting to a PipeName like \msagent_de5f that Event 17 shows was created moments earlier by an unrelated process confirms two distinct processes are actively communicating over that pipe, consistent with inter-stage C2 handoff.
Sample record
Pipe Connected:
RuleName: -
EventType: ConnectPipe
UtcTime: 2024-02-11 09:41:27.118
ProcessGuid: {a1b2c3d4-1234-65a1-0000-001122334455}
ProcessId: 6120
PipeName: \msagent_de5f
Image: C:\Windows\Temp\stager.exe
User: CORP\jdoeSources
Paste a record into Event XML or open a log in EVTX Reader.