Malicious RTF — malware analysis report

Static analysis result for SHA-256 41c5bb9eeb301b53…

MALICIOUS

RTF

14.2 KB First seen: 2018-07-27
MD5: 5ac12a82e506da55d8d8668d393acc19 SHA-1: 090089ae6962c85adc1de87ff78dde40467455bc SHA-256: 41c5bb9eeb301b53796a0b3d526c965e3eea6e634a4863643729d93b03b4808b
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 4148 bytes
SHA-256: a2c99f5ad6b4509c2ff7f2e20fec7cbd588496cf34904268b767da18bb75fc57