Malicious RTF — malware analysis report

Static analysis result for SHA-256 f0aa64e048ba6e05…

MALICIOUS

RTF

25.0 KB
MD5: c4d7770f7d9230c9b9167a4327ae32c7 SHA-1: 2a4da64a856e2afe4fc99972056e19652f03a307 SHA-256: f0aa64e048ba6e054e31b86ae0dfdaee0dcdab73e324e7bb926c9dccdee63a14
120 Risk Score

Malware Insights

MITRE ATT&CK
T1566.002 Spearphishing Attachment T1204.002 Malicious File T1027 Obfuscated Files or Information

The RTF document contains embedded OLE objects, indicated by RTF_OBJDATA and RTF_OBJEMB heuristics. The RTF_OBJUPDATE heuristic suggests that these objects are designed to be activated, likely to execute embedded code or launch a secondary payload. The RTF_OLE10NATIVE_STREAM further confirms the presence of a decoded OLE object, which is a common technique for delivering malicious content within documents.

Heuristics 4

  • 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 2 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001829.bin
b6318498dd8f19f912509c8a1d714a2f36bbb65218610ad65b0ebb7a80e06b14
rtf-objdata-decoded RTF \objdata at offset 0x1829 4180 bytes