Malicious RTF — malware analysis report

Static analysis result for SHA-256 643d685722c8e1b9…

MALICIOUS

RTF

24.2 KB First seen: 2023-03-13
MD5: ec0db75f4e0ded2359ced29d46f0e6d6 SHA-1: 6e92b01a2969c0cf0cc1279066e899c3e2588ecd SHA-256: 643d685722c8e1b94f076da9fb21a38bb37a62a1f6d54956bc26a68137fa24b9
100 Risk Score

Malware Insights

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

The sample is an RTF document containing OLE object data that forces activation via \objupdate. This indicates an attempt to exploit OLE vulnerabilities or execute embedded code. The presence of \objdata and \objupdate heuristics strongly suggests a malicious OLE object is embedded within the RTF, likely intended to download and execute a secondary payload.

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_off00001f4a.bin
e0f0acf79c86022a16c03964fb8766b870fd1b71271c181a50b09cc9f9beab1c
rtf-objdata-decoded RTF \objdata at offset 0x1F4A 3657 bytes