Malicious RTF — malware analysis report

Static analysis result for SHA-256 294780752a8070c5…

MALICIOUS

RTF

14.1 KB First seen: 2018-11-13
MD5: 7ad9336cd6e913f425ca4f4ffe19ebb5 SHA-1: 7880afd661a483fb9550d1292ae89b0eabe9ebfb SHA-256: 294780752a8070c56dad657ede640e272a0fa166bd5a56d75c982b4d22d384df
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_off00000802.bin rtf-objdata-decoded RTF \objdata at offset 0x802 4135 bytes
SHA-256: d9b97695cd4d9f5339030082ed1138a829050c2a1bfd9e67f0600e2ce656e54b