Windows Maldoc Process Injection via winword.exe CallTrace from LittleCorporal

Flags winword.exe process injection where the call trace matches LittleCorporal-generated Maldoc activity on Windows.

FreeReviewedSigma · High · v2
Product
windows
Category
process_access
Author
Christian Burkard (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-08-09
Updated
2026-07-31

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule flags process injection activity where the source process is winword.exe and the call stack contains a .NET Framework64 v2 path alongside an UNKNOWN marker. This pattern is associated with maldoc-driven injection generated by the LittleCorporal tool, where an attacker attempts to run malicious code inside a trusted Office process. The detection relies on process access telemetry capturing the injecting source image and call trace contents.

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 Maldoc Process Injection via winword.exe CallTrace from LittleCorporal
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.