Office (OLE) malware analysis — malicious · 6012fa11458a9b5d

MALICIOUS

Office (OLE)

103.2 KB Created: 2006-01-25 08:30:00 Authoring application: Microsoft Office Word

MD5: 861a9ec174ac1092cc5ed6544f9cc2f8 SHA-1: e87f3bb138df3bfbd561195dd8ee7e96c4eda757 SHA-256: 6012fa11458a9b5d49ae6c92af2a49632d16693d0996b9c0abad6929c7b12285

260 Risk Score

Malware Insights

MITRE ATT&CK

T1059.003 Windows Command Shell T1204.002 Malicious File

The sample exhibits high-confidence heuristics indicating the execution of cmd.exe and the use of Windows API functions for process creation and library loading. The OLE slack anomaly suggests potential obfuscation or embedded malicious content. These findings point to an attempt to execute a secondary payload, likely for further system compromise.

Heuristics 7

Reference to WinExec API high SC_STR_WINEXEC

Reference to WinExec API
Reference to CreateProcess API high SC_STR_CREATEPROCESS

Reference to CreateProcess API
Suspicious cmd.exe invocation with execution flag high SC_STR_CMD

Suspicious cmd.exe invocation with execution flag
Reference to LoadLibrary API high SC_STR_LOADLIBRARY

Reference to LoadLibrary API
Reference to GetProcAddress API high SC_STR_GETPROCADDRESS

Reference to GetProcAddress API
OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY

OLE file is 105,632 bytes but its declared streams total only 21,151 bytes — 84,481 bytes (80%) live in unallocated sector slack. This is the canonical hiding place for pre-macro-era Office exploit payloads (XOR-encoded shellcode reached via a parser pointer-corruption bug in the document structure).
Reference to VirtualAlloc API medium SC_STR_VIRTUALALLOC

Reference to VirtualAlloc API

Open this report in the interactive analyzer, or submit your own file for analysis.