Malicious RTF — malware analysis report

Static analysis result for SHA-256 893a1f9039279c4d…

MALICIOUS

RTF

26.2 KB
MD5: 23527c2589d9347ba19bfa5ed02737da SHA-1: 7da1e4636f800921dad1159acaff468bc688a86e SHA-256: 893a1f9039279c4d0776fe6bfa1df3d0722c803e824b3fcbb93b4a2e61966119
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data that is forced to activate via \objupdate. This indicates the document is designed to exploit RTF parsing vulnerabilities or embed malicious objects. The presence of OLE object data and the \objupdate directive strongly suggest a malicious intent to execute embedded code or launch an external payload upon opening.

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_off00001c58.bin
6bc8b81c26b53a6de5208a33c2a71f0a2183573625beb85feb21130f617f5a8f
rtf-objdata-decoded RTF \objdata at offset 0x1C58 4193 bytes