Malicious RTF — malware analysis report

Static analysis result for SHA-256 3388d7947e4a88f9…

MALICIOUS

RTF

14.1 KB First seen: 2018-07-27
MD5: e1732badb52a8c8e47c502ca40d71b13 SHA-1: d7beda23a9114dc13e1f1313370f76d7aecd7ece SHA-256: 3388d7947e4a88f9abddda3bdf86e80a8dc50297564fb12cd1ada12430945273
100 Risk Score

Malware Insights

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

The RTF document contains embedded OLE object data, indicated by RTF_OBJDATA and RTF_OLE10NATIVE_STREAM heuristics. The RTF_OBJUPDATE heuristic suggests that the embedded object is designed to be activated automatically, likely leading to the execution of a malicious payload. No specific family could be identified, and no further IOCs were extracted.

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_off00000800.bin rtf-objdata-decoded RTF \objdata at offset 0x800 4133 bytes
SHA-256: 554c366d498446ca598b7db30d0c2622a12058f68a567dceb3b8eed7e24b90ce