Detection rules › Splunk

Windows Service Create RemComSvc

Status
production
Severity
low
Group by
ImagePath, ServiceType, dest, service_name
Author
Michael Haag, Splunk
Source
github.com/splunk/security_content

The following analytic detects the creation of the RemComSvc service on a Windows endpoint, typically indicating lateral movement using RemCom.exe. It leverages Windows EventCode 7045 from the System event log, specifically looking for the "RemCom Service" name. This activity is significant as it often signifies unauthorized lateral movement within the network, which is a common tactic used by attackers to spread malware or gain further access. If confirmed malicious, this could lead to unauthorized access to sensitive systems, data exfiltration, or further compromise of the network.

Known false positives

  • False positives may be present, filter as needed based on administrative activity.

MITRE ATT&CK coverage

Telemetry coverage

Rule body

name: Windows Service Create RemComSvc
id: 0be4b5d6-c449-4084-b945-2392b519c33b
version: 10
creation_date: '2023-03-20'
modification_date: '2026-05-13'
author: Michael Haag, Splunk
status: production
type: Anomaly
description: The following analytic detects the creation of the RemComSvc service on a Windows endpoint, typically indicating lateral movement using RemCom.exe. It leverages Windows EventCode 7045 from the System event log, specifically looking for the "RemCom Service" name. This activity is significant as it often signifies unauthorized lateral movement within the network, which is a common tactic used by attackers to spread malware or gain further access. If confirmed malicious, this could lead to unauthorized access to sensitive systems, data exfiltration, or further compromise of the network.
data_source:
    - Windows Event Log System 7045
search: |-
    `wineventlog_system` EventCode=7045 ServiceName="RemCom Service"
      | stats count min(_time) as firstTime max(_time) as lastTime
        BY dest ImagePath ServiceName
           ServiceType
      | `security_content_ctime(firstTime)`
      | `security_content_ctime(lastTime)`
      | `windows_service_create_remcomsvc_filter`
how_to_implement: To implement this analytic, the Windows EventCode 7045 will need to be logged. The Windows TA for Splunk is also recommended.
known_false_positives: False positives may be present, filter as needed based on administrative activity.
references:
    - https://www.crowdstrike.com/blog/bears-midst-intrusion-democratic-national-committee/
    - https://github.com/kavika13/RemCom
intermediate_findings:
    entities:
        - field: dest
          type: system
          score: 20
          message: A new service was created related to RemCom on $dest$.
analytic_story:
    - Active Directory Discovery
asset_type: Endpoint
mitre_attack_id:
    - T1543.003
product:
    - Splunk Enterprise
    - Splunk Enterprise Security
    - Splunk Cloud
category: endpoint
security_domain: endpoint

Stages and Predicates

Stage 1: search

`wineventlog_system` EventCode=7045 ServiceName="RemCom Service"

Stage 2: stats

| stats count min(_time) as firstTime max(_time) as lastTime
    BY dest ImagePath ServiceName
       ServiceType

Stage 3: search

| `security_content_ctime(firstTime)`

Stage 4: search

| `security_content_ctime(lastTime)`

Stage 5: search

| `windows_service_create_remcomsvc_filter`

Indicators

These rows show field, operator, and value matches.

FieldKindValuesSearch
EventCodeeq
  • 7045 corpus 21 (splunk 18, elastic 1, chronicle 1, kusto 1)
field:"EventID" kind:eq value:"7045"
ServiceNameeq
  • "RemCom Service"
field:"ServiceName" kind:eq