PUA - RemCom Default Named Pipe

calendar Aug 12, 2024 · attack.lateral-movement attack.t1021.002 attack.execution attack.t1569.002  ·
Share on: linkedin copy

Detects default RemCom pipe creation

Sigma rule (View on GitHub)

 1title: PUA - RemCom Default Named Pipe
 2id: d36f87ea-c403-44d2-aa79-1a0ac7c24456
 3related:
 4    - id: 9e77ed63-2ecf-4c7b-b09d-640834882028
 5      type: obsolete
 6status: test
 7description: Detects default RemCom pipe creation
 8references:
 9    - https://drive.google.com/file/d/1lKya3_mLnR3UQuCoiYruO3qgu052_iS_/view
10    - https://github.com/kavika13/RemCom
11author: Nikita Nazarov, oscd.community, Nasreddine Bencherchali (Nextron Systems)
12date: 2023-08-07
13modified: 2023-11-30
14tags:
15    - attack.lateral-movement
16    - attack.t1021.002
17    - attack.execution
18    - attack.t1569.002
19logsource:
20    product: windows
21    category: pipe_created
22    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'
23detection:
24    selection:
25        PipeName|contains: '\RemCom'
26    condition: selection
27falsepositives:
28    - Legitimate Administrator activity
29level: medium

References

Related rules

to-top