Windows Service Create SliverC2

Try in Splunk Security Cloud

Description

When an adversary utilizes SliverC2 to laterally move with the Psexec module, it will create a service with the name and description of "Sliver" and "Sliver Implant". Note that these may be easily changed and are specific to only SliverC2. We have also created the same regex as Microsoft has outlined to attempt to capture the suspicious service path (regex101 reference).

• Type: TTP

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

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

Annotations

ATT&CK

ATT&CK

ID	Technique	Tactic
T1569	System Services	Execution

T1569.002

Service Execution

Execution

Kill Chain Phase

• Installation

NIST

• DE.CM

CIS20

• CIS 3
• CIS 5
• CIS 16

CVE

Search

`wineventlog_system` EventCode=7045 ServiceName="sliver" 
| stats count min(_time) as firstTime max(_time) as lastTime by Computer EventCode ImagePath ServiceName ServiceType 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `windows_service_create_sliverc2_filter`

Macros

The SPL above uses the following Macros:

• wineventlog_system
• security_content_ctime

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.

• UPDATE

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

• BishopFox Sliver Adversary Emulation Framework

RBA

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

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

Reference

• https://github.com/BishopFox/sliver/blob/71f94928bf36c1557ea5fbeffa161b71116f56b2/client/command/exec/psexec.go#LL61C5-L61C16
• https://www.microsoft.com/en-us/security/blog/2022/08/24/looking-for-the-sliver-lining-hunting-for-emerging-command-and-control-frameworks/
• https://regex101.com/r/DWkkXm/1

Test Dataset

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

• https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1055/sliver/sliver_windows-system.log

source | version: 1