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

Static analysis result for SHA-256 eab469349938b7fe…

MALICIOUS

Office (OLE) / .DOC

142.8 KB
MD5: 3d9da556d09f9fe2a3575c5f12b9c31b SHA-1: 6b93cb1e431b94ca623e7964a45540e72acfd281 SHA-256: eab469349938b7fe70a0165645590b0501d391ed00f6699b8050fc88f4d39b44
120 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The OLE document exhibits significant slack space, a common technique for obfuscating malicious content. Heuristics indicate references to LoadLibrary and GetProcAddress APIs, often used by malware to dynamically load and execute code. The document body contains references to embedded OLE objects like Excel and PowerPoint, which could be used to deliver further payloads.

Heuristics 3

  • 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 146,180 bytes but its declared streams total only 31,351 bytes — 114,829 bytes (79%) 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).