Malicious RTF — malware analysis report

Static analysis result for SHA-256 1d534f3b35965c98…

MALICIOUS

RTF

19.5 KB
MD5: 95f851252339b1db19f787399aa98ba8 SHA-1: 43107cf0df9c973e8a07f75c8557a4bbc2415bd7 SHA-256: 1d534f3b35965c986d6c69ddcf4f050c1568f60a22c9d3c155799e1078ce6af3
100 Risk Score

Malware Insights

MITRE ATT&CK
T1566.002 Spearphishing Attachment T1204.002 Malicious File

The RTF document contains OLE objects that are configured to activate automatically upon opening, indicated by the RTF_OBJDATA and RTF_OBJUPDATE heuristics. This suggests the document is designed to exploit OLE object handling to execute embedded malicious content. 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 2 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000af2.bin
b7e444ac9d47b1c779784d7f84e3c20cdd035082f90492f011f0b785db79b076
rtf-objdata-decoded RTF \objdata at offset 0xAF2 3668 bytes