Windows File Creation: ProgramData Persistence Artifacts Matching

Alerts on Windows file creations in C:\ProgramData matching specific driver inf, .dll, and batch/script filename patterns.

FreeReviewedSigma · High · v5
Product
windows
Category
file_event
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2024-04-23
Updated
2026-07-31

ATT&CK techniques

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags Windows file creation events where the target filename is under C:\ProgramData\ and matches specific patterns associated with driver-store style entries or named payload artifacts. Such activity is notable because attackers may drop or stage executables and scripts in commonly writable locations like ProgramData to support persistence or post-compromise tooling. It relies on file event telemetry that includes the full target filename/path and matches it using prefix, suffix, and substring conditions.

Related detections9 linkedT1685.001 — drag to rearrange
Malicious Security Event Log Disabled via wevtutil
Malicious SQL Server Auditing Deactivated (via application)
Malicious Event Log Deactivation or Size Reduction - Command (via process_creation)
Malicious Audit Policy Disabled by Command Line (via process_creation)
Suspicious IIS Logging Disabled via appcmd
Malicious SQL Server Database Auditing Deactivated (via application)
Malicious Audit Policy Disabled by Command Line (via security)
Malicious Event Log Tampering via wevtutil Channel Disable by FunkSec Ransomware (via process_creation)
OCSP Responder Auditing Settings Changed or Disabled (via security)
Windows File Creation: ProgramData Persistence Artifacts Matching
Pivot detection · T1685.001 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.