Malicious RTF — malware analysis report

Static analysis result for SHA-256 f954beddea657599…

MALICIOUS

RTF

14.2 KB First seen: 2019-11-20
MD5: 9df9cd818dc11704ca15be8c03622771 SHA-1: d12ec5e67921f06927c25596cc3c5cedf9f7667b SHA-256: f954beddea657599699648ab48ad6387a551ccb7d9555170875d76af78b359d6
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_off00000801.bin rtf-objdata-decoded RTF \objdata at offset 0x801 4156 bytes
SHA-256: 8bed0037da57b0ebaad1abd19f6883bad43bf0228c15fefab602b63fd80c1cc4