Detection rules › Sigma

Malicious Windows Script Components File Execution by TAEF Detection

Severity
low
Author
Agro (@agro_sev) oscd.community
Source
upstream

Windows Test Authoring and Execution Framework (TAEF) framework allows you to run automation by executing tests files written on different languages (C, C#, Microsoft COM Scripting interfaces Adversaries may execute malicious code (such as WSC file with VBScript, dll and so on) directly by running te.exe

MITRE ATT&CK coverage

TacticTechniques
Defense EvasionT1218 System Binary Proxy Execution

Event coverage

ProviderEvent IDTitle
Sysmon1Process creation

Stages and Predicates

Stage 1: selection

or:
Image|endswith: '\te.exe'
OriginalFileName: '\te.exe'
ParentImage|endswith: '\te.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.

FieldKindValues
Imageends_with
  • \te.exe
OriginalFileNameeq
  • \te.exe
ParentImageends_with
  • \te.exe