Windows ISO File Creation in User Temp and Outlook Cache Folders

Alerts on creation of .iso files in Windows AppData temp or Outlook cache paths.

FreeReviewedSigma · High · v2
Product
windows
Category
file_event
Author
@sam0x90 (SigmaHQ), DRL 1.1
Published
2022-07-30
Updated
2026-07-31

ATT&CK techniques

Initial Access
  1. Recon

  2. Resource Dev

  3. Execution

  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 identifies file creation events where an ISO file is written to common temporary storage locations, including the AppData Local Temp folder or Outlook-related INetCache content. Attackers may stage ISO images in these directories to support subsequent execution steps while reducing visibility in typical application paths. It relies on Windows file event telemetry that includes the created file path in TargetFilename and supports matching on folder substrings and a .iso suffix.

Related detections9 linkedT1566.001 — drag to rearrange
Suspicious mstsc Launch of RDP File From User Download or Temp Path (via process_creation)
Suspicious Regsvr32 Squiblydoo Remote Scriptlet Execution via Command Line (via process_creation)
Possible Mamba 2FA AiTM Phishing URL Pattern
Suspicious DLL Written to Explorer IconCache Path
Suspicious DNS Query to HTML Smuggling AiTM Phishing Domain
Malicious Microsoft Word Spawning Anomalous Child Process via CVE-2023-36884 (via process_creation)
Malicious Equation Editor Child Process Execution via process_creation
Microsoft 365 inbound suspicious email delivered to Inbox or Junk
Web Browser Opens .HTM/.HTML from Downloads Folder on Windows
Windows ISO File Creation in User Temp and Outlook Cache Folders
Pivot detection · T1566.001 · 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.