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

Static analysis result for SHA-256 26b3b6401d2d35b5…

MALICIOUS

Office (OLE) / .TMP

145.2 KB Created: 2001-12-14 14:26:00 Authoring application: Microsoft Word 9.0
MD5: 21e744d2ee02bf6408b35023544a9cc8 SHA-1: 31c32bb166c4b11b2fda93e381bfe5b7a11529ee SHA-256: 26b3b6401d2d35b5bd727d17f6dd88f9dc96d994cdda0763c77c185b08d157cb
102 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File T1566.001 Spearphishing Attachment

The sample is a Microsoft Word document that contains a critical heuristic indicating exploitation of CVE-2006-6456, a vulnerability related to malformed tables. Additionally, the OLE file has an appended executable payload. No VBA macros could be extracted, but the presence of these indicators strongly suggests a malicious document designed to exploit this vulnerability and deliver a secondary payload.

Heuristics 3

  • 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 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.
  • Unsupported Office format for VBA extraction info OFFICE_FORMAT_UNSUPPORTED
    olevba could not extract VBA macros (PermissionError); format-agnostic byte-level scans still ran. Likely legacy, encrypted, or malformed OLE/OOXML — re-scanning the same bytes will yield the same outcome.