Windows: Copying Executable or DLL Files into Default GPO Policies Folder

Alerts when .exe/.dll files are created in the default GPO storage folder path.

FreeReviewedSigma · Medium · v2
Product
windows
Category
file_event
Author
elhoim (SigmaHQ), DRL 1.1
Published
2022-04-28
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies file creation events where the target path includes the default GPO storage folder GUID and the file name ends with .exe or .dll. Attackers may stage malicious executables or libraries in GPO-related locations to increase the chance of later execution via policy application. It relies on Windows file event telemetry that provides the created/target filename path and extension.

Related detections9 linkedT1036.005 — drag to rearrange
Suspicious Loading of Masqueraded EndpointDlp.dll Backdoor
Suspicious svchost.exe Execution from Public Directory (via process_creation)
Suspicious Process Masquerading as apached via GobRAT Bulbature Implant
Suspicious MicrosoftEdgeUpdate Launched with Dat Config File
Malicious Scheduled Task Masquerading as Defender NisSrv via Schtasks
Malicious PowerShell Masquerading as Windows Terminal in ProgramData (via process_creation)
Suspicious Csrss Process Masquerading Outside System32 (via process_creation)
Suspicious Mimilite Credential Dumper Execution Writing KB-Named Output
Suspicious PikaBot Autorun Persistence Pointing to AppData Microsoft Dropzone via registry_set
Windows: Copying Executable or DLL Files into Default GPO Policies Folder
Pivot detection · T1036.005 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.