Detection rules › Splunk
GetWmiObject User Account with PowerShell Script Block
The following analytic detects the execution of the Get-WmiObject commandlet with the Win32_UserAccount parameter via PowerShell Script Block Logging (EventCode=4104). This method leverages script block text to identify when a list of all local users is being enumerated. This activity is significant as it may indicate an adversary or Red Team operation attempting to gather user information for situational awareness and Active Directory discovery. If confirmed malicious, this could lead to further reconnaissance, privilege escalation, or lateral movement within the network.
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Execution | T1059.001 Command and Scripting Interpreter: PowerShell |
| Discovery | T1087.001 Account Discovery: Local Account |
Event coverage
| Provider | Event ID | Title |
|---|---|---|
| PowerShell | 4104 | Creating Scriptblock text (MessageNumber of MessageTotal). |
Stages and Predicates
Stage 1: search
search EventCode=4104 ScriptBlockText="*Get-WmiObject*" ScriptBlockText="*Win32_UserAccount*"
Stage 2: fillnull
fillnull
Stage 3: stats
stats BY dest, signature, signature_id, user_id, vendor_product, EventID, Guid, Opcode, Name, Path, ProcessID, ScriptBlockId, ScriptBlockText
Stage 4: search
search
Stage 5: search
search
Stage 6: search
search `macro`
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 |
|
ScriptBlockText | eq |
|
Neighbors
Broader alternatives (more inclusive than this rule)
These rules match a superset of what this rule catches. They cover the same events plus more. Use them if you want wider coverage and can absorb more false positives.
- Potential PowerShell Obfuscation via Invalid Escape Sequences (drops 3 filters this rule applies)
- Potential PowerShell Obfuscation via Backtick-Escaped Variable Expansion (drops 3 filters this rule applies)
- Potential PowerShell Obfuscation via Character Array Reconstruction (drops 3 filters this rule applies)
- Potential PowerShell Obfuscation via Concatenated Dynamic Command Invocation (drops 3 filters this rule applies)
- Potential PowerShell Obfuscation via High Numeric Character Proportion (drops 3 filters this rule applies)
- Potential Dynamic IEX Reconstruction via Environment Variables (drops 3 filters this rule applies)
- Dynamic IEX Reconstruction via Method String Access (drops 3 filters this rule applies)
- PowerShell Obfuscation via Negative Index String Reversal (drops 3 filters this rule applies)
- Potential PowerShell Obfuscation via Reverse Keywords (drops 3 filters this rule applies)
- Potential PowerShell Obfuscation via String Concatenation (drops 3 filters this rule applies)
- Potential PowerShell Obfuscation via String Reordering (drops 3 filters this rule applies)
- Potential PowerShell Obfuscation via Special Character Overuse (drops 3 filters this rule applies)
- PowerShell 4104 Hunting (drops 2 filters this rule applies)