Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 071795252708c3e8…

MALICIOUS

Office (OLE)

446.0 KB Created: 2001-12-14 14:26:00 Authoring application: Microsoft Word 9.0
MD5: 109a3a95ba6f5a736523e38b12087255 SHA-1: 4c7f9402a2860c58f296736fe52d8a72bea22457 SHA-256: 071795252708c3e82078f78ac1825c1c6470230a72a9156b58a092631b17cb75
142 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The sample is a Microsoft Word document exhibiting significant OLE slack space and an appended executable payload, indicating it is designed to deliver malicious code. The critical heuristic firing for CVE-2006-6456 confirms exploitation of a known Microsoft Word vulnerability for client execution. While the document body contains garbled text, the presence of embedded URLs suggests a potential lure or download source, though their reputation is mixed. No scripts were extracted from this sample.

Heuristics 4

  • CVE-2006-6456 — Microsoft Word malformed table SPRM critical CVE exact CVE_2006_6456
    WordDocument contains a malformed table border-color SPRM in the CVE-2006-6456 shape: a valid table-SPRM cluster is followed by an invalid high-byte 0xFF SPRM where Word expects a normal sprmTBrc*Cv record. Vulnerable Word 2000/2002/2003 parsers corrupt memory while handling this malformed data structure.
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 456,752 bytes but its declared streams total only 94,801 bytes — 361,951 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).
  • 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.
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://www.samefacts.com/images/800px-Flag_of_Tibet.svg.png
    • http://blog.163.com/qhhlzx_007/blog/static/443803201031513017215/
    • http://picasaweb.google.com.au/aenpokyabgon/AllKyegu2010EarthquakePhotos?feat=directlink#