Malicious RTF — malware analysis report

Static analysis result for SHA-256 352d223c2deab5bc…

MALICIOUS

RTF

19.3 KB First seen: 2018-09-04
MD5: 4c0b7932a006f68e79487001b6ad7921 SHA-1: e0a49cd01fba3e860138e3958b1d94def94f88b1 SHA-256: 352d223c2deab5bc4185470d5a2c08fe3c852589fc6e4d70dd8b324947887516
100 Risk Score

Malware Insights

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

The sample is an RTF document containing OLE object data and an \objupdate directive, indicating an attempt to exploit OLE activation for code execution. The presence of these elements strongly suggests a spearphishing attachment used to deliver a malicious payload. No specific family could be identified from the available evidence.

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_off00001675.bin rtf-objdata-decoded RTF \objdata at offset 0x1675 4649 bytes
SHA-256: ae2f1802c30b8ddd81c5e57d7fab92ff46cd486b7bc6671baf41cbaea65c8af8