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
- Datamodel: Endpoint
- Last Updated: 2021-04-26
- Author: Teoderick Contreras, Splunk
- ID: 1804b0a4-a682-11eb-8f68-acde48001122
|T1055||Process Injection||Defense Evasion, Privilege Escalation|
`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`
Associated Analytic Story
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. .
Kill Chain Phase
Known False Positives
|42.0||70||60||Possible Trickbot namedpipe created on $Computer$ by $Image$|
source | version: 1