Suspicious AutoIt Execution from PIF File Masquerade

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-06-10
Updated
2026-08-28

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects an AutoIt interpreter running with a pif extension image such as Flour.pif from a user writable location. This masquerade delivered an RC4 decrypted Vidar Stealer payload in the KMSPico drive-by chain. Renaming the AutoIt engine to a pif hides script based execution from casual review.

Related detections9 linkedT1027 — drag to rearrange
Suspicious Encoded PowerShell Using Base64 Stream Decompression Routines (via process_creation)
Suspicious PowerShell In-Memory Execution with AES Decryption
Suspicious Encoded PowerShell Command Execution
Suspicious node.exe Executing Compiled JavaScript Bytecode File
Malicious Encoded Payload Decoded and Piped to Shell via xxd or base64 (via process_creation)
Suspicious PEAKLIGHT Memory-Only PowerShell Downloader Flags (via process_creation)
Suspicious Fake GIF Magic Header Written to Disguise Payload File (via process_creation)
Suspicious Base64 Decode Piped to Python Interpreter for In-Memory Execution (via process_creation)
Suspicious Thumbs.ini File Written to AppData by UNC2970 MISTPEN (via file_event)
Suspicious AutoIt Execution from PIF File Masquerade
Pivot detection · T1027 · 9 related

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