Windows PowerShell Copies a DLL into System32 or SysWOW64

Flags PowerShell Copy-Item targeting Windows\System32 or Windows\SysWOW64 for file placement.

FreeReviewedSigma · High · v2
Product
windows
Category
ps_script
Author
frack113, Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-12-27
Updated
2026-07-31

ATT&CK techniques

Persistence → Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Priv Esc

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule matches PowerShell script block content where a file copy command (e.g., Copy-Item/cpi) copies a DLL into a Windows system directory, specifically paths under \Windows\System32 or \Windows\SysWOW64. Attackers may use this to place malicious or unwanted DLLs where they can later be loaded by legitimate processes, supporting persistence or defense impairment. Telemetry relies on script block logging that captures the executed PowerShell text and its destination path.

Related detections3 linkedT1556.002 — drag to rearrange
Malicious Ntospy Network Provider DLL Registration for Credential Capture
Windows Process Creation: Suspicious secedit.exe Security Policy Export or Configuration
Windows Credential Access via Reg Add in LSA Registry Paths
Windows PowerShell Copies a DLL into System32 or SysWOW64
Pivot detection · T1556.002 · 3 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.