Malicious RTF — malware analysis report

Static analysis result for SHA-256 3c3c542991a93f69…

MALICIOUS

RTF

14.2 KB First seen: 2019-04-18
MD5: f8432ab623ce1621fd3864296adeaedd SHA-1: e29bb3100c2f8e262eb71e61160c9a02a79f3e33 SHA-256: 3c3c542991a93f6933d51ce5e4f91b5e55d060bbf7f5cfab821d10a144b02e0e
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_off000007ff.bin rtf-objdata-decoded RTF \objdata at offset 0x7FF 4155 bytes
SHA-256: 72aeb701d8c81ecadb520661aec2b44de7de34aa4071886ad1f12f18a40328e6