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

Static analysis result for SHA-256 a134bc7207a13a02…

MALICIOUS

Office (OLE) / .DOC

191.8 KB Created: 2008-03-05 03:19:00 Authoring application: Microsoft Office Word
MD5: 9dc76b579a54033baa109c682b8e8e3b SHA-1: 1285f3dbd7466ca47bf751b1856ea666dc9e5eac SHA-256: a134bc7207a13a024b90beef5d63c80acd9ffe9bedb47965016f1bb439f1246e
100 Risk Score

Malware Insights

MITRE ATT&CK
T1027 Obfuscated Files or Information

The sample exhibits characteristics of a malicious document, specifically the presence of XOR-encoded strings and a significant amount of slack space within the OLE structure. These techniques are commonly used for obfuscation and evasion. While no specific payload or delivery mechanism is directly evident from the provided heuristics and document body, the combination strongly suggests malicious intent, likely to conceal a secondary stage.

Heuristics 2

  • XOR-encoded strings (key 0x63) critical SC_XOR_ENCODED
    Found 4 Windows library/API name(s) XOR-encoded with single-byte key 0x63: 'LoadLibraryA', 'CreateProcessA', 'ExitProcess', 'CreateFileA'
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 196,424 bytes but its declared streams total only 20,635 bytes — 175,789 bytes (89%) 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).