Windows Named Pipe Creation with CoercedPotato Pipe Name Pattern

title: Windows Named Pipe Creation with CoercedPotato Pipe Name Pattern
id: f2de4ecd-e2b1-46ab-8ecc-b0fd66d0db74
status: test
description: This rule flags Windows named pipe creation events where the pipe name contains the substring '\coerced\'. Named pipes are commonly used for stealthy inter-process communication, and attackers may create specific pipe names to coordinate actions during privilege escalation. It relies on telemetry that records named pipe creation, such as Sysmon named pipe events that include the created PipeName.
references:
  - https://blog.hackvens.fr/articles/CoercedPotato.html
  - https://github.com/hackvens/CoercedPotato
  - https://github.com/SigmaHQ/sigma/blob/master/rules/windows/pipe_created/pipe_created_hktl_coercedpotato.yml
author: Florian Roth (Nextron Systems), Huntrule Team
date: 2023-10-11
tags:
  - attack.privilege-escalation
  - attack.stealth
  - attack.t1055
logsource:
  product: windows
  category: pipe_created
  definition: Note that you have to configure logging for Named Pipe Events in Sysmon config (Event ID 17 and Event ID 18). The basic configuration is in popular sysmon configuration (https://github.com/SwiftOnSecurity/sysmon-config), but it is worth verifying. You can also use other repo, e.g. https://github.com/Neo23x0/sysmon-config, https://github.com/olafhartong/sysmon-modular. How to test detection? You can check powershell script from this site https://svch0st.medium.com/guide-to-named-pipes-and-hunting-for-cobalt-strike-pipes-dc46b2c5f575
detection:
  selection:
    PipeName|contains: \coerced\
  condition: selection
falsepositives:
  - Unknown
level: high
license: DRL-1.1
related:
  - id: 4d0083b3-580b-40da-9bba-626c19fe4033
    type: derived