Malicious RTF — malware analysis report

Static analysis result for SHA-256 afb43d1988553bf4…

MALICIOUS

RTF

22.5 KB First seen: 2021-11-02
MD5: 99715802ac102615e878b70092f9ce11 SHA-1: 167b213a49bd6d67a4bac25ad312f5b4873b0c82 SHA-256: afb43d1988553bf4fe7f4d9e4422b7c39651259de1ed558628b67cb340aac398
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data and uses \objupdate to force activation. This indicates an attempt to leverage OLE object vulnerabilities or features for malicious purposes. While no specific payload or script was directly extracted, the heuristics strongly suggest the document is designed to execute embedded code or trigger a download. The lack of readable document body text or scripts prevents a more specific determination of the attack's intent.

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_off00001679.bin
804f66491933da80ac0e462480b63a9c55eb4c854f0e2e87e61b1d574ff15a37
rtf-objdata-decoded RTF \objdata at offset 0x1679 3665 bytes