Detection rules › Splunk

Abuse EQNEDT32.EXE (EDR)

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

Detects potential malicious Microsoft Office payload (CVE-2017-11882 or CVE-2018-0798) on host. Equation Editor

MITRE ATT&CK coverage

References

Event coverage

Rule body yaml

id: '1074.16965'
title: Abuse EQNEDT32.EXE
description: 'Detects potential malicious Microsoft Office payload (CVE-2017-11882
  or CVE-2018-0798) on host. Equation Editor. -- Threat Actor Association: Bitter
  APT, Lotus Blossom, SideWinder, TA428, Tonto Team - Software Association: Soul'
logic_format: Splunk
logic: ' `get_endpoint_data` `get_endpoint_data_edr` ((event_type IN ("childproc","netconn","proc"))
  OR (TERM(ProcessRollup2) OR Type=Process) OR TERM(DeviceProcessEvents)) "EQNEDT32.EXE"
  | table _time, host, user _time, host, session_id, process, signature_id, parent_process_name,
  process_name, user | bin span=300s | stats values(*) as * by _time, host | where
  match(parent_process_name, "(?i)EQNEDT32.EXE") | table _time, host, user _time,
  host, session_id, process, signature_id, parent_process_name, user `hec_collect`'
techniques:
- execution:exploitation for client execution
technique_id: 
- T1203
data_category:
- EDR Logs
references:
- https://www.fireeye.com/blog/threat-research/2017/12/targeted-attack-in-middle-east-by-apt34.html

Stages and Predicates

Stage 1: search

`get_endpoint_data` `get_endpoint_data_edr` ((event_type IN ("childproc","netconn","proc")) OR (TERM(ProcessRollup2) OR Type=Process) OR TERM(DeviceProcessEvents)) "EQNEDT32.EXE"

Stage 2: table

| table _time, host, user _time, host, session_id, process, signature_id, parent_process_name, process_name, user

Stage 3: bucket

| bin span=300s

Stage 4: stats

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

Stage 5: where

| where match(parent_process_name, "(?i)EQNEDT32.EXE")

Stage 6: table

| table _time, host, user _time, host, session_id, process, signature_id, parent_process_name, user `hec_collect`

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
event_typein
  • "childproc"
  • "netconn"
  • "proc"
parent_process_namematch
  • "(?i)EQNEDT32.EXE" corpus 3 (splunk 3)

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
1TERM
1ProcessRollup2
1TERM
1DeviceProcessEvents
1"EQNEDT32.EXE"