Office (OLE) / .DOC malware analysis — malicious · a3c6c36ebe1446e3

MALICIOUS

Office (OLE) / .DOC

151.9 KB

MD5: 21e457e853d0b462ce809b7ccb99548a SHA-1: a11922de491513af3aa5829250116941c616ecdc SHA-256: a3c6c36ebe1446e37e9aacbd197414f90df8fee59e5a39e2af7dbcaee9e3a36f

180 Risk Score

Malware Insights

MITRE ATT&CK

T1204.002 Malicious File T1059.001 PowerShell T1059.003 Windows Command Shell

The OLE document exhibits a significant slack space anomaly, indicating potential obfuscation or embedded malicious content. Heuristics indicate the use of ShellExecute, VirtualAlloc, LoadLibrary, and GetProcAddress APIs, commonly employed by malware to load and execute code. While no scripts were explicitly extracted, the combination of these API calls suggests the document is designed to download and run a second-stage payload.

Heuristics 5

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 155,584 bytes but its declared streams total only 31,351 bytes — 124,233 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.