Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 7b6a3f5f885e0067…

MALICIOUS

RTF / .DOC

634.7 KB
MD5: 4c8e90937a0516f48aa3b8cb17cbc7b8 SHA-1: 89b8ff3dbb714d2ff658e0c09a65dbc590e19da4 SHA-256: 7b6a3f5f885e00679f66af1168236c12b3db888689fe8bb7879f994f4160c352
80 Risk Score

Malware Insights

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

The sample is an RTF document containing an embedded OLE object, indicated by the RTF_OBJDATA heuristic. The RTF_OBJUPDATE heuristic suggests that this object is designed to be activated automatically upon opening or when the user enables editing, as prompted by the SE_ENABLE_LURE heuristic. This points to an attack pattern where the document exploits user interaction to execute embedded malicious content, likely a second-stage payload.

Heuristics 3

  • \objupdate forces OLE activation high RTF_OBJUPDATE
    RTF contains \objupdate — forces automatic OLE object instantiation when the document is opened, bypassing user interaction. Almost exclusively seen in Equation Editor exploit documents.
  • OLE object data medium RTF_OBJDATA
    RTF contains 1 \objdata section(s) — embedded OLE objects
  • Macro/content-enable lure medium SE_ENABLE_LURE
    Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000bcf7.bin
5b63cd02a441f37b4fc870c67ea8403d84a48d1a59d496f0617ae78140e94cfc
rtf-objdata-decoded RTF \objdata at offset 0xBCF7 3736 bytes