Detection rules › Splunk
IcedID Discovery Commands (Sysmon)
IcedID may automatically run several initial discovery commands that provided environmental information about the host, network, and domain. This use case looks for a combination of those commands commonly seen after IcedID is executed
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Discovery | T1069.002 Permission Groups Discovery: Domain Groups, T1082 System Information Discovery, T1087 Account Discovery, T1135 Network Share Discovery |
| Collection | T1119 Automated Collection |
References
Event coverage
| Provider | Event | Title |
|---|---|---|
| Sysmon | Event ID 1 | Process creation |
Rule body yaml
id: '12911.18538'
title: IcedID Discovery Commands
description: IcedID may automatically run several initial discovery commands that
provided environmental information about the host, network, and domain. This use
case looks for a combination of those commands commonly seen after IcedID is executed.
- Living Off the Land Binary and Scripts (LOLBAS) (LOLBIN)
logic_format: Splunk
logic: '`get_endpoint_data` `get_endpoint_data_sysmon` (TERM(EventCode=1) OR "<EventID>1<")
("net.exe" OR "net1.exe" OR "ipconfig" OR "ipconfig.exe" OR "nltest" OR "nltest.exe"
OR "systeminfo" OR "systeminfo.exe") | table _time, host, user process, process_*,
signature_id, parent_* | bin span=60s | stats values(*) as * by _time, host | where
match(process_name, "(?i)systeminfo.exe") and match(process_name, "(?i)net1?.exe")
and match(process_name, "(?i)nltest.exe") and match(process_name, "(?i)ipconfig.exe") '
techniques:
- discovery:permission groups discovery:domain groups
- discovery:network share discovery
- discovery:account discovery
- discovery:system information discovery
- collection:automated collection
technique_id:
- T1069.002
- T1135
- T1087
- T1082
- T1119
data_category:
- Windows Sysmon
references:
- https://thedfirreport.com/2022/04/25/quantum-ransomware/
Stages and Predicates
Stage 1: search
`get_endpoint_data` `get_endpoint_data_sysmon` (TERM(EventCode=1) OR "<EventID>1<") ("net.exe" OR "net1.exe" OR "ipconfig" OR "ipconfig.exe" OR "nltest" OR "nltest.exe" OR "systeminfo" OR "systeminfo.exe")
Stage 2: table
| table _time, host, user process, process_*, signature_id, parent_*
Stage 3: bucket
| bin span=60s
Stage 4: stats
| stats values(*) as * by _time, host
Stage 5: where
| where match(process_name, "(?i)systeminfo.exe") and match(process_name, "(?i)net1?.exe") and match(process_name, "(?i)nltest.exe") and match(process_name, "(?i)ipconfig.exe")
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.
| Field | Kind | Values |
|---|---|---|
EventCode | eq |
|
process_name | match |
|
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.
| Stage | Term |
|---|---|
| 1 | TERM |
| 1 | "<EventID>1<" |
| 1 | "net.exe" |
| 1 | "net1.exe" |
| 1 | "ipconfig" |
| 1 | "ipconfig.exe" |
| 1 | "nltest" |
| 1 | "nltest.exe" |
| 1 | "systeminfo" |
| 1 | "systeminfo.exe" |