Malicious RTF — malware analysis report

Static analysis result for SHA-256 5157ca16df40efbb…

MALICIOUS

RTF

17.3 KB First seen: 2018-10-07
MD5: 39584a59da7a58a95e1ba0b1f6d0773b SHA-1: a630f96da6df0707faf08f9b975e702031d51d22 SHA-256: 5157ca16df40efbb46503491f7075ca7a8f4379246007430ad10155a1b868748
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 4666 bytes
SHA-256: fb9746fba50d9f39e835f9ebcfb69bf70e31d3adbc69c32e3dd160cf1b397d67