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

Static analysis result for SHA-256 7752c48b0e059246…

MALICIOUS

Office (OLE) / .DOC

89.0 KB Created: 2009-02-26 07:53:00 Authoring application: Microsoft Office Word
MD5: 8f0eac14641e24a729e739e2be5c608c SHA-1: ee3465cec74e17726c699c6decb33aa1a3f976f9 SHA-256: 7752c48b0e0592467221f272e63404da910bf2528711a812cc6612771f6cc644
140 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The file is identified as malicious due to the presence of an appended executable payload and a significant amount of slack space within the OLE structure. These characteristics are indicative of a dropper or a similar malware delivery mechanism. The XOR-encoded strings further suggest obfuscation techniques commonly employed by malware. No specific family could be identified.

Heuristics 3

  • XOR-encoded strings (key 0xC2) critical SC_XOR_ENCODED
    Found 2 Windows library/API name(s) XOR-encoded with single-byte key 0xC2: 'advapi32.dll', 'RegOpenKeyExA'
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 91,137 bytes but its declared streams total only 16,543 bytes — 74,594 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).
  • OLE file has appended executable-looking payload bytes high OLE_APPENDED_PAYLOAD
    OLE compound file contains a large high-entropy region beyond the declared major streams and that region includes shellcode, PE, or loader API markers. This is a payload-carrier signal, not a specific CVE attribution by itself.