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

Static analysis result for SHA-256 706f4b36c3aa4955…

MALICIOUS

Office (OLE) / .RTF

182.8 KB
MD5: 6b2a6e91d6940664c6ff9ffb4ce35cdf SHA-1: 4528f0616b74c71018e732386f85ad4998911c00 SHA-256: 706f4b36c3aa4955c1e7acf8c0747f86d755dd1775ff4c16005d2684397a566e
80 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment

The RTF document exhibits characteristics of a dropper, with a significant portion of its file size comprising appended executable payload bytes. The OLE slack anomaly further indicates potential obfuscation or packing of malicious content within the file structure. No specific family could be identified, but the pattern suggests a malicious attachment designed to deliver a secondary payload.

Heuristics 2

  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 187,136 bytes but its declared streams total only 12,338 bytes — 174,798 bytes (93%) 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.