Windows: Suspicious Cabinet (CAB) File Expansion via expand.exe from Uncommon Paths

Flags expand.exe ("-F:") extracting cabinets when used from suspicious/uncommon Windows paths.

FreeReviewedSigma · Medium · v2
Product
windows
Category
process_creation
Author
Bhabesh Raj, X__Junior (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-07-30
Updated
2026-07-31

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 flags Windows executions of expand.exe with the -F argument that expand CAB files originating from potentially suspicious or uncommon directories (e.g., Perflogs, ProgramData, Public, Windows Temp, Admin$ shares, Temp under AppData). Attackers may use this behavior to extract embedded payloads or staging files while blending into normal-looking system activity. It relies on process creation telemetry capturing Image and CommandLine, including parent process context.

Related detections9 linkedT1218 — drag to rearrange
Suspicious Renamed Windows Debugger CDB Execution
Suspicious Scripting Interpreter Execution From Downloads Or Temp via Reputation Hijacking
Suspicious MMC Console Spawning Script Interpreter via GrimResource
Suspicious MMC Console Loading MSC File From User Writable Path
Suspicious Cabinet Extraction of Masqueraded vstm Archive via extrac32
Malicious DLL Execution via Wuauclt Update Handler (via process_creation)
Malicious aspnet_compiler.exe Injection Host Spawned by PowerShell via process_creation
Malicious regsvcs LOLBin Loading Ransomware DLL from UNC Path
Suspicious RegAsm or RegSvcs Spawned by Script Host (via process_creation)
Windows: Suspicious Cabinet (CAB) File Expansion via expand.exe from Uncommon Paths
Pivot detection · T1218 · 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.