Suspicious PUA - RemCom Default Named Pipe (via pipe_created)

This rule detects default RemCom pipe creation

SigmamediumWindowsv1
sigma
title: Suspicious PUA - RemCom Default Named Pipe (via pipe_created)
id: 831ad34c-8d51-5c3b-b28b-d15965b7289b
status: stable
description: This rule detects default RemCom pipe creation
references:
    - https://attack.mitre.org/techniques/T1569/002/
    - https://attack.mitre.org/techniques/T1021/002/
    - https://drive.google.com/file/d/1lKya3_mLnR3UQuCoiYruO3qgu052_iS_/view
    - https://github.com/kavika13/RemCom
author: Huntrule Team
date: 2026-07-15
tags:
    - attack.lateral-movement
    - attack.t1021.002
    - attack.execution
    - attack.t1569.002
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: '\RemCom'
    condition: selection
falsepositives:
    - Unknown
level: medium

Known false positives

  • Unknown

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.