Detection rules › Splunk

Remote Thread from Suspicious Folder (Sysmon)

Group by
_time, host, parent_process_name
Source
github.com/anvilogic-forge/armory

Detects potential remote threads created from suspicious file locations like temp, appdata, and downloads

MITRE ATT&CK coverage

TacticTechniques
Privilege EscalationT1055 Process Injection
StealthT1055 Process Injection

Event coverage

ProviderEventTitle
SysmonEvent ID 8CreateRemoteThread

Rule body yaml

id: '9020.12093'
title: Remote Thread from Suspicious Folder
description: 'Detects potential remote threads created from suspicious file locations
  like temp, appdata, and downloads. - Threat Actor Association: APT10/menuPass, TA413
  - Software Association: Black Basta, LOWZERO'
logic_format: Splunk
logic: '`get_endpoint_data` `get_endpoint_data_sysmon` (EventCode=8 OR "Event>ID>8<")
  ("Temporary Internet Files" OR TERM("TEMP") OR TERM("Downloads") OR TERM("Appdata"))
  | regex parent_process_path="(?i)Temp|Downloads|Appdata" | table _time, host, user
  dest, direction, event_id, eventtype, parent_*, process, process_*, user, user_id
  | bin span=1s | stats values(*) as * by _time, host, parent_process_path '
techniques:
- defense-evasion:process injection
- privilege-escalation:process injection
technique_id: 
- T1055
data_category:
- Process command-line parameters
- Windows Sysmon
references: null

Stages and Predicates

Stage 1: search

`get_endpoint_data` `get_endpoint_data_sysmon` (EventCode=8 OR "Event>ID>8<") ("Temporary Internet Files" OR TERM("TEMP") OR TERM("Downloads") OR TERM("Appdata"))

Stage 2: regex

| regex parent_process_path="(?i)Temp|Downloads|Appdata"

Stage 3: table

| table _time, host, user dest, direction, event_id, eventtype, parent_*, process, process_*, user, user_id

Stage 4: bucket

| bin span=1s

Stage 5: stats

| stats values(*) as * by _time, host, parent_process_path

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
EventCodeeq
  • 8 corpus 11 (splunk 11)
parent_process_pathregex_match
    • "(?i)Temp
    • Downloads
    • Appdata"

Search terms

Bare-string tokens in the SPL search body. Splunk matches each token against _raw (the untyped raw event text) anywhere it appears, not against a specific field. These don't surface in the Indicators table because they aren't predicates on a known field.

StageTerm
1"Event>ID>8<"
1"Temporary Internet Files"
1"TEMP"
1"Downloads"
1"Appdata"