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

Static analysis result for SHA-256 974ec991a85910ea…

MALICIOUS

Office (OLE) / .DOC

61.3 KB Created: 2005-06-29 18:14:00 Authoring application: Microsoft Word 10.0
MD5: 4c44fcc2f5404f9380e508c6e3f2a007 SHA-1: 0e1e8659987f433a63bc86b0f63a69ede5feafab SHA-256: 974ec991a85910ea039279940b976c32ae4ab07a9f2e07e3bc538bc780603afb
80 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The sample is an OLE document with a significant amount of slack space, indicating potential obfuscation or embedded malicious content. A high-severity heuristic firing for CreateProcess API suggests the document is designed to launch an external process. The document body is heavily corrupted and unreadable, providing no further context on the lure. Without readable document body or script content, the exact payload and delivery mechanism remain unclear, leading to an unknown family classification.

Heuristics 2

  • Reference to CreateProcess API high SC_STR_CREATEPROCESS
    Reference to CreateProcess API
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 62,754 bytes but its declared streams total only 20,632 bytes — 42,122 bytes (67%) 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).