Windows Suspicious EXE in User Directory Launched by Microsoft Office Applications

Alert on Office spawning a .exe from C:\users\ (except when the child is Teams.exe).

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Jason Lynch (SigmaHQ), DRL 1.1
Published
2019-04-02
Updated
2026-07-30

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 process executions where an Office application (Word, Excel, PowerPoint, Publisher, Visio, Access, or Equation Editor) starts an executable located under the user directory (C:\users\) that ends with .exe. Such behavior matters because it can indicate user-writable execution paths used to run malware or unauthorized payloads from Office-launched processes. It relies on Windows process creation telemetry, specifically the parent process image and the child process image path.

Related detections9 linkedT1204.002 — drag to rearrange
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)
Uncommon Executable Written to Startup Folder by WinRAR via CVE-2025-8088 Path Traversal (via file_event)
Malicious KB Document Masqueraded Executable Spawned by Script Interpreter via RoKRAT Loader (via process_creation)
Windows Suspicious EXE in User Directory Launched by Microsoft Office Applications
Pivot detection · T1204.002 · 9 related

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