Invoke-Obfuscation Via Use MSHTA - Security
Detects Obfuscated Powershell via use MSHTA in Scripts
Sigma rule (View on GitHub)
1title: Invoke-Obfuscation Via Use MSHTA - Security
2id: 9b8d9203-4e0f-4cd9-bb06-4cc4ea6d0e9a
3related:
4 - id: 7e9c7999-0f9b-4d4a-a6ed-af6d553d4af4
5 type: derived
6status: test
7description: Detects Obfuscated Powershell via use MSHTA in Scripts
8references:
9 - https://github.com/SigmaHQ/sigma/issues/1009 # (Task31)
10author: Nikita Nazarov, oscd.community
11date: 2020-10-09
12modified: 2022-11-29
13tags:
14 - attack.defense-evasion
15 - attack.t1027
16 - attack.execution
17 - attack.t1059.001
18logsource:
19 product: windows
20 service: security
21 definition: The 'System Security Extension' audit subcategory need to be enabled to log the EID 4697
22detection:
23 selection:
24 EventID: 4697
25 ServiceFileName|contains|all:
26 - 'mshta'
27 - 'vbscript:createobject'
28 - '.run'
29 - 'window.close'
30 condition: selection
31falsepositives:
32 - Unknown
33level: high
References
Related rules
- ConvertTo-SecureString Cmdlet Usage Via CommandLine
- Invoke-Obfuscation CLIP+ Launcher
- Invoke-Obfuscation CLIP+ Launcher - PowerShell
- Invoke-Obfuscation CLIP+ Launcher - PowerShell Module
- Invoke-Obfuscation CLIP+ Launcher - Security