Windows Suspicious File Creation in C:\PerfLogs with Executable/Script Extensions

Alerts on creation of potentially malicious file types in C:\PerfLogs\ on Windows.

FreeReviewedSigma · Medium · v2
Product
windows
Category
file_event
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-05-05
Updated
2026-07-31

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags file creation events where the target path starts with C:\PerfLogs\ and the filename ends with a list of executable or script-related extensions. Attackers may use this directory to stage or drop payloads where it blends with existing logging/performance artifacts. The detection relies on Windows file event telemetry that records the created file path and extension.

Related detections9 linkedT1059 — drag to rearrange
Suspicious OneNote Spawning Command or Script Interpreter via Spear-Phishing (via process_creation)
Malicious Web Server Process Spawning Command Interpreter via Web Shell (via process_creation)
Suspicious VMware Guest Operation Output Staging in vmware-system Temp Directory (via file_event)
Malicious Command Shell Spawned by SQL Server via Process Creation (via process_creation)
Suspicious Script Interpreter Spawned by Excel via DarkGate Lure
Suspicious AutoHotkey Script Execution from User Writable Path by DarkGate
Malicious China Chopper Web Shell Command Pattern in IIS Worker Process (via process_creation)
Malicious AutoHotKey Runner AutoNotify Executing AHKBot Looper Script (via process_creation)
Malicious IIS Worker Process Spawning Command Shell after ASP.NET ViewState Injection (via process_creation)
Windows Suspicious File Creation in C:\PerfLogs with Executable/Script Extensions
Pivot detection · T1059 · 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.