Office (OLE) malware analysis — malicious · 30f7336b194bee39

MALICIOUS

Office (OLE)

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

MD5: 9da93ad971eb8528b7fd2e83135e61e5 SHA-1: d8f3d410946d90e9338bfe57c9d8da6d27159df0 SHA-256: 30f7336b194bee398a15c90f1f6ff215d19176887005d8417b53cdb65ec7d826

340 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 PowerShell T1059.003 Windows Command Shell T1204.002 Malicious File T1105 Ingress Tool Transfer T1055.012 Process Hollowing

The heuristics indicate the document leverages Windows API functions such as WinExec, ShellExecute, VirtualAlloc, WriteProcessMemory, CreateRemoteThread, LoadLibrary, and GetProcAddress. This strongly suggests the document is designed to execute arbitrary code, likely by injecting it into another process. The OLE slack anomaly further points to a packed or obfuscated payload within the document. Without a document body or scripts, the exact lure and delivery mechanism remain unclear, leading to a lower confidence in family attribution.

Heuristics 8

Reference to WriteProcessMemory API critical SC_STR_WRITEPROCESSMEMORY

Reference to WriteProcessMemory API
Reference to CreateRemoteThread API critical SC_STR_CREATEREMOTETHREAD

Reference to CreateRemoteThread API
Reference to WinExec API high SC_STR_WINEXEC

Reference to WinExec API
Reference to ShellExecute API high SC_STR_SHELLEXEC

Reference to ShellExecute API
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 140,704 bytes but its declared streams total only 21,151 bytes — 119,553 bytes (85%) 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.