Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 10e9665be878b1d0…

MALICIOUS

RTF / .DOC

85.6 KB
MD5: 9e1d036df3064629b26e4715f0353cd5 SHA-1: bf17e5e2c3bdd306d773f75344599c97e83a6fea SHA-256: 10e9665be878b1d0936bbbdfe7a2b2c5bcc0539fbcbc02a871d1b4b533fe16a3
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data and uses \objupdate to force OLE activation, indicating an attempt to exploit a vulnerability for client execution. The presence of the Ole10Native stream further supports this. The specific exploit mechanism is not detailed, but the overall pattern suggests a malicious attachment designed to compromise the user's system.

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_off000011e7.bin
2481f2ab67a5e0db12935c3effcf04f750fa541e9f28730ff5e6bf243becb3bb
rtf-objdata-decoded RTF \objdata at offset 0x11E7 4805 bytes