Malicious RTF — malware analysis report

Static analysis result for SHA-256 0bedc8c5a5a48ee1…

MALICIOUS

RTF

14.2 KB First seen: 2018-10-07
MD5: c82b98e5367900d22e988af9e545e5ae SHA-1: abf241af59cf4bf472230b57ce48de892e3cd79c SHA-256: 0bedc8c5a5a48ee1728ac0a0416a5243a17c4440e60974cf3941d42d767735ec
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 4155 bytes
SHA-256: 5aa993db4dc45bfc89e84aff4ae9a5797f2f1b1fcdc676165454703c43b058a7