Detectionlowtest
Malicious Windows Script Components File Execution by TAEF Detection
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
Convert In Phoenix Studio
Open this Sigma rule in the converter with the YAML preloaded and ready for backend selection.
Launch
Log Source
WindowsProcess Creation
ProductWindows← raw: windows
CategoryProcess Creation← raw: process_creation
Events generated when a new process is spawned on the system. Covers command-line arguments, parent/child relationships, and process metadata.
Detection Logic
Detection Logic1 selector
detection:
selection:
- Image|endswith: '\te.exe'
- ParentImage|endswith: '\te.exe'
- OriginalFileName: '\te.exe'
condition: selectionFalse Positives
It's not an uncommon to use te.exe directly to execute legal TAEF tests
MITRE ATT&CK
Tactics
Techniques
Rule Metadata
Rule ID
634b00d5-ccc3-4a06-ae3b-0ec8444dd51b
Status
test
Level
low
Type
Detection
Created
Tue Oct 13
Modified
Sat Nov 27
Author
Path
rules/windows/process_creation/proc_creation_win_susp_use_of_te_bin.yml
Raw Tags
attack.defense-evasionattack.t1218