Windows Office Applications Creating Executable/Script Files with Suspicious Extensions

Flags Office application processes creating .exe/.dll/.ps1 and other script or executable files on Windows.

FreeReviewedSigma · High · v2
Product
windows
Category
file_event
Author
Vadim Khrykov (ThreatIntel), Cyb3rEng (Rule), Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-08-23
Updated
2026-07-31

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  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 file creation events where a Microsoft Office process (Excel, Access, Publisher, PowerPoint, Visio, or Word) creates files ending in executable or script extensions. Attackers may use Office applications to drop and execute payloads or staging components using these commonly abused file types. The detection relies on Windows file event telemetry containing the creating process image path and the created target filename, with exclusions for specific known cache/temp locations to reduce noise.

Related detections9 linkedT1204.002 — drag to rearrange
Suspicious OneNote Spawning Script Interpreter (via process_creation)
Suspicious vbc.exe Spawned by Installer Process
Suspicious n8n Campaign RMM Installer Masquerading as OneDrive Document
Suspicious NFe-Themed Brazilian Lure Executable Execution
Suspicious Executable Dropped in Public Users Directory Named Ctrlpanel (via file_event)
Suspicious Interlock Fake Updater Executable Execution
Malicious Office Application Loading a User-Path DLL via Regsvr32 or Rundll32 (via process_creation)
Suspicious Program Execution From a Mounted ISO or Disk Image (via process_creation)
SocGholish Fake Browser Update Script Execution (via process_creation)
Windows Office Applications Creating Executable/Script Files with Suspicious Extensions
Pivot detection · T1204.002 · 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.