Windows Mock Trusted Directory MSC File Creation
Detects the creation of MSC files within a "C:\Windows \System32" directory. Due to how Windows parses paths, the space causes an execution flow hijack and a malicious file will be executed instead of the standard…
Description
Detects the creation of MSC files within a "C:\Windows \System32" directory. Due to how Windows parses paths, the space causes an execution flow hijack and a malicious file will be executed instead of the standard Windows Files.
Detection logic
Detection requirements
- Platform
- LinuxmacOSWindows
The rule states no platform. This is derived from the 3 ATT&CK techniques it maps to.
- Log source category
- sysmon_eventid_11
Known benign triggers
- Some legitimate software installers or system maintenance tools may create MSC files in the System32 directory with unusual paths. Verify and allow trusted system or vendor-approved processes to reduce false positives.
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 |
|---|---|
| www.fortinet.com/blog/threat-research/fickle-stealer-distributed-via-multiple-attack-chain | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- de8cc077-2dba-4060-af78-c98b3cfc5407
- Tagged by the source as
- Windows Persistence TechniquesWindows Privilege EscalationEndpointendpointSplunk CloudSplunk EnterpriseSplunk Enterprise Securityendpoint
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1