Windows Winword.exe Creates INetCache .cab and .inf Files During CVE-2021-40444 Exploitation

Flags winword.exe writing CABs in INetCache or INF files in Temp consistent with CVE-2021-40444 exploitation.

FreeReviewedSigma · High · v5
Product
windows
Category
file_event
Author
Florian Roth (Nextron Systems), Sittikorn S (SigmaHQ), DRL 1.1
Published
2021-09-10
Updated
2026-07-31

ATT&CK techniques

Resource Dev
  1. Recon

  2. Initial Access

  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 flags Windows file creation activity where winword.exe writes a .cab file into the INetCache directory or creates a .inf file under AppData\Local\Temp. Such patterns can indicate document-triggered payload staging, where attacker-controlled files are dropped to transient locations for follow-on execution. It relies on file event telemetry capturing the process image path and the created target filename, including directory and extension details.

Related detections5 linkedT1587 — drag to rearrange
Linux process execution matches known hacktools by image name
Windows DLL Hijacking via Forced Load of C:\Windows\ADFS\version.dll
Windows File Events: PoC Filename Pattern for CVE-2021-1675 Spooler Exploitation
Windows Execution of PurpleSharp HackTool by Image Name or Executable Metadata
Linux Auditd: Program Executions from Suspicious Web and Data Directories
Windows Winword.exe Creates INetCache .cab and .inf Files During CVE-2021-40444 Exploitation
Pivot detection · T1587 · 5 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.