Malicious RTF — malware analysis report

Static analysis result for SHA-256 5d6af79217df3d4e…

MALICIOUS

RTF

17.3 KB First seen: 2019-02-10
MD5: 918e3fcc62d4b370894b651f7c51acec SHA-1: 74288546f7ce052f7068b59d2233a43263044481 SHA-256: 5d6af79217df3d4ea7427d76c3b652dd133255fca54a6d6263c56ef3997f4b8c
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: d01d849060fd78078b09a1d084961befb9546d057b8f2a036fdd5d8c54a3b784