Malicious Office (OLE) / .DOC — malware analysis report

Static analysis result for SHA-256 f7189962fcefc76a…

MALICIOUS

Office (OLE) / .DOC

174.0 KB
MD5: 7ea8976affebd7058b07fe5185a23210 SHA-1: 5fbaa7664a15eddaba12fcd0ba687b3ed068811d SHA-256: f7189962fcefc76a6522a54bd433cb601ede617650d802ee01c5154f310035c0
140 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.002 Malicious File T1055 Process Injection

The OLE document exhibits a significant slack anomaly, indicating potential obfuscation or embedded malicious content. High-severity heuristics for VirtualAlloc, LoadLibrary, and GetProcAddress suggest the document is designed to dynamically load and execute code. The presence of these APIs strongly implies an attempt to download and run a second-stage payload, characteristic of many Office-based malware delivery mechanisms.

Heuristics 4

  • 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 178,176 bytes but its declared streams total only 31,351 bytes — 146,825 bytes (82%) 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