Malicious RTF — malware analysis report

Static analysis result for SHA-256 7b538fe19172ddda…

MALICIOUS

RTF

675.3 KB First seen: 2019-05-10
MD5: 3c37e892f28dd6a3084be7f3d551e5dc SHA-1: 1a31832ab206b6c2253a449d3a9d50dad99d46b7 SHA-256: 7b538fe19172ddda87126ed04b21a11245eb73f259ba21d1833ab04144e24c61
100 Risk Score

Malware Insights

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

The RTF file contains OLE object data with an \objupdate directive, indicating an attempt to exploit a vulnerability for client execution. The presence of OLE object data and the \objupdate heuristic strongly suggest that the file is designed to trigger an exploit when opened. Given the malicious verdict and exploit indicators, it is highly probable that this file is delivered as a spearphishing attachment intended to download and execute a secondary payload.

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_off00001f55.bin rtf-objdata-decoded RTF \objdata at offset 0x1F55 5973 bytes
SHA-256: ce38ea989633e0fbf039177c7d2871f6259cbab322cbb63d06eb84b2eb19d8e1