Suspicious Command Output Redirection to Windows Debug Out File (via process_creation)

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-10-06
Updated
2026-10-06

ATT&CK techniques

Collection
  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. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects command execution that redirects output to the hardcoded C\Windows\debug\out.txt file. This behavior was observed in attacks against industrial organizations where second-stage commands capture their results to a fixed file under the Windows debug directory for later collection. Detecting this reveals hands-on-keyboard reconnaissance and output staging.

Related detections9 linkedT1074.001 — drag to rearrange
Suspicious Archive Staging to ProgramData NetWorks Path via RAR (via process_creation)
Malicious Empyrean Stealer Staging Files in AppData (via file_event)
TerraStealerV2 Data Staging in Bay0NsQIzx Package Directory (via file_event)
Suspicious C2Looper Shell Output Artifact File Creation (via file_event)
Malicious Kimsuky Troll Stealer Collected Data Staging Files with gte1 Extension (via file_event)
Suspicious VOLTZITE Single-Character Named ZIP Exfil Staging (via file_event)
PowerShell Classic Compress-Archive staging in TEMP or Temp directories
PowerShell Compress-Archive Creates Archive in Temp or System Temp Paths
PowerShell: Compress-Archive to TEMP/AppData/Windows Temp for Staging
Suspicious Command Output Redirection to Windows Debug Out File (via process_creation)
Pivot detection · T1074.001 · 9 related

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