Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 0e8042810f803695…

MALICIOUS

RTF / .DOC

28.7 KB
MD5: 5242db71a9b5092dd951c947bb741164 SHA-1: 75d729a8e8c2359625c8f5761c8d9afa16b6ce40 SHA-256: 0e8042810f803695fa289c786f2ce51171276667da5e8a5ffd63f247dd06b056
100 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects, indicated by the RTF_OBJDATA and RTF_OLE10NATIVE_STREAM heuristics. The RTF_OBJUPDATE heuristic suggests that these objects are automatically activated upon opening the document, which is a common technique for exploiting vulnerabilities like CVE-2017-11882 to achieve code execution. The presence of these indicators strongly suggests an attempt to exploit a client execution vulnerability, likely delivered as a spearphishing attachment.

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 2 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001845.bin
c9b2372e4b4606b6830d00f17c2439648026a4fe8e261fc91ee4d489c521a6e7
rtf-objdata-decoded RTF \objdata at offset 0x1845 4176 bytes