Malicious RTF — malware analysis report

Static analysis result for SHA-256 9e420111c70dccde…

MALICIOUS

RTF

17.4 KB First seen: 2019-01-12
MD5: 76693f0c22b2e5b7a0a90fd56d2728d7 SHA-1: 7e345fd7c682d06d957ea3b98c7ccfaf95fdf434 SHA-256: 9e420111c70dccde5584340e6fe2c0dc28920cfa81ab35a97ea5655bfda4c370
100 Risk Score

Malware Insights

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

The RTF file contains OLE object data and uses \objupdate to force activation, indicating an attempt to exploit OLE vulnerabilities for execution. The embedded OLE object, decoded as 'objdata_00_off00000ef3.bin', is the primary artifact of interest. Without further script or body content, the exact payload and delivery mechanism remain unclear, but the technique strongly suggests a malicious attachment designed to execute arbitrary code.

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_off00000ef3.bin rtf-objdata-decoded RTF \objdata at offset 0xEF3 4664 bytes
SHA-256: cdfb2ca19e88371b2b71e4f870ba1097c3023300af7e878f33290d3245ec531f