Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 83407fc51abcd839…

MALICIOUS

RTF / .DOC

76.1 KB
MD5: 8e7e27108101528880376d901d0e9133 SHA-1: 9617e0724407680bd7df1f3d7e91e4078b2012ba SHA-256: 83407fc51abcd83933c49f85c1567b8abf479293334ce9ecaa4cd9715b2cad4e
100 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects that are forced to activate via \objupdate, indicating an attempt to execute embedded content. The presence of RTF_OLE10NATIVE_STREAM further suggests that a native OLE object is present, which is commonly used to deliver second-stage malware. While no specific script or URL was extracted, the heuristics strongly suggest a malicious document designed to exploit RTF parsing for initial execution.

Heuristics 3

  • Ole10Native stream in RTF OLE object high CVE related RTF_OLE10NATIVE_STREAM
    RTF contains an embedded OLE object with an Ole10Native stream. This is a strong payload-container signal and is related to Word/OLE exploit delivery, but it is not specific enough on its own to assign a CVE.
  • \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

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000013e7.bin
ef692b4f213482c7991ec7df1732f88c02d3eb11676c1a486dbb8c818714057b
rtf-objdata-decoded RTF \objdata at offset 0x13E7 4186 bytes