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 Python Execution via Renamed Synaptics Binary
MSBuild Executing Non-Project File or Remote Payload
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Possible Craft CMS RCE via Query-String CLI Option Injection
Possible Aspera Faspex Pre-Auth RCE via YAML Deserialization in package_relay (via webserver)
Possible Sitecore Pre-Auth RCE via Report.ashx Insecure Deserialization (via webserver)
Possible WatchGuard Pre-Auth RCE via agent login XML-RPC CVE-2022-26318
Possible Oracle Opera CGI Webshell Command Execution via operabin
Suspicious tar Extraction of Staged Archive to Temp (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.