Trickbot Named Pipe

Description

this search is to detect potential trickbot infection through the create/connected named pipe to the system. This technique is used by trickbot to communicate to its c2 to post or get command during infection.

Type: TTP
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
Last Updated: 2021-04-26
Author: Teoderick Contreras, Splunk
ID: 1804b0a4-a682-11eb-8f68-acde48001122

Annotations

ATT&CK

ID	Technique	Tactic
T1055	Process Injection	Defense Evasion, Privilege Escalation

Kill Chain Phase

Exploitation

NIST

DE.CM

CIS20

CIS 10

CVE

Search

`sysmon` EventCode IN (17,18) PipeName="\\pipe\\*lacesomepipe" 
| stats  min(_time) as firstTime max(_time) as lastTime count by Computer user_id EventCode PipeName signature Image process_id 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `trickbot_named_pipe_filter`

Macros

The SPL above uses the following Macros:

trickbot_named_pipe_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.

_time
Computer
user_id
EventCode
PipeName
signature
Image
process_id

How To Implement

To successfully implement this search, you need to be ingesting logs with the process name and pipename from your endpoints. If you are using Sysmon, you must have at least version 6.0.4 of the Sysmon TA. .

Known False Positives

unknown

Associated Analytic Story

Trickbot

RBA

Risk Score	Impact	Confidence	Message
42.0	70	60	Possible Trickbot namedpipe created on $Computer$ by $Image$

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

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

source | version: 1

Twitter Facebook LinkedIn