Malicious RTF — malware analysis report

Static analysis result for SHA-256 490dffae713877fb…

MALICIOUS

RTF

55.8 KB First seen: 2018-11-13
MD5: f83639d0eec661a1548e031ce8b48df3 SHA-1: b8f72f5719d2aab08129821e8dcc56358fb0e013 SHA-256: 490dffae713877fb70613e60ea91e72333d19855fb249d2d6666bab4152005be
100 Risk Score

Malware Insights

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

The RTF file contains OLE object data and an \objupdate directive, indicating an attempt to exploit OLE object handling for execution. The embedded OLE object is likely a payload, though its specific nature cannot be determined from static analysis alone. The document body is benign, suggesting the maliciousness relies entirely on the embedded object.

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_off000000fc.bin rtf-objdata-decoded RTF \objdata at offset 0xFC 16395 bytes
SHA-256: dfe3883ba7a71c5489dbedda6d589e7f424bd6b268bb0ff91ff93de59ba688cc