Try in Splunk Security Cloud


The following analytic detects the creation of a Windows service named "Sliver" with the description "Sliver Implant," indicative of SliverC2 lateral movement using the PsExec module. It leverages Windows EventCode 7045 from the System Event log to identify this activity. This behavior is significant as it may indicate an adversary's attempt to establish persistence or execute commands remotely. If confirmed malicious, this activity could allow attackers to maintain control over the compromised system, execute arbitrary code, and further infiltrate the network.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2024-05-25
  • Author: Michael Haag, Splunk
  • ID: 89dad3ee-57ec-43dc-9044-131c4edd663f




ID Technique Tactic
T1569 System Services Execution
T1569.002 Service Execution Execution
Kill Chain Phase
  • Installation
  • DE.CM
  • CIS 10
`wineventlog_system` EventCode=7045 ServiceName="sliver" 
| stats count min(_time) as firstTime max(_time) as lastTime by Computer EventCode ImagePath ServiceName ServiceType 
| rename Computer as dest 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `windows_service_create_sliverc2_filter`


The SPL above uses the following Macros:

:information_source: windows_service_create_sliverc2_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

  • EventCode
  • Computer
  • ServiceName
  • ImagePath
  • ServiceType

How To Implement

To implement this analytic, the Windows EventCode 7045 will need to be logged from the System Event log. The Windows TA for Splunk is also recommended.

Known False Positives

False positives should be limited, but if another service out there is named Sliver, filtering may be needed.

Associated Analytic Story


Risk Score Impact Confidence Message
90.0 90 100 A user mode service was created on $dest$ related to SliverC2.

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.


Test Dataset

Replay any dataset to Splunk Enterprise by using our tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 2