Registry Manipulation via WMI Stdregprov
Detects the usage of wmic.exe to modify Windows registry via the WMI StdRegProv class write methods (CreateKey, DeleteKey, SetStringValue, etc.). This behaviour could be potentially suspicious because it uses an…
Description
Detects the usage of wmic.exe to modify Windows registry via the WMI StdRegProv class write methods (CreateKey, DeleteKey, SetStringValue, etc.). This behaviour could be potentially suspicious because it uses an alternative method to modify registry keys instead of legitimate registry tools like reg.exe or regedit.exe. Attackers specifically choose this technique to evade detection and bypass security monitoring focused on traditional registry modification commands.
Detection logic
Detection requirements
- Platform
- Windows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source product
- windows
- Log source category
- process_creation
Known benign triggers
- Legitimate administrative activity
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| learn.microsoft.com/en-us/previous-versions/windows/desktop/regprov/stdregprov | 3from 2 sources |
| trustedsec.com/blog/command-line-underdog-wmic-in-action | 2 |
| trustedsec.com/blog/wmi-for-script-kiddies | 2 |
| www.bitdefender.com/en-us/blog/businessinsights/shrinklocker-decryptor-from-friend-to-foe-and-back-again | 2from 2 sources |
From the source
- At source
- Open at source
- Upstream identifier
- c453ab7a-1f5c-4716-a3b4-dea8135fb43a
- Tagged by the source as
- attack.defense-impairmentattack.executionattack.persistence
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1