Malicious RTF — malware analysis report

Static analysis result for SHA-256 3321e72b105bf45e…

MALICIOUS

RTF

20.4 KB
MD5: 1f8aafaa7066d000524d7a5b9f44380c SHA-1: 20cd7fbaebc83129a097cd230c64c989af59dc29 SHA-256: 3321e72b105bf45ec576adccf32d96c1e56238e7e8eaa1dfb4b745df318dd801
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data and triggers OLE activation via \objupdate, indicating it's designed to embed and execute external content. The presence of \objupdate and the Ole10Native stream strongly suggest the document is a malicious OLE container. While no specific payload or URL was directly extracted, the heuristics point to a classic OLE-based attack vector for delivering further malware.

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_off00000680.bin
e345bb7dafb36d88483bb43c40304ce156911c7b7b01817bac8fa2701cff9531
rtf-objdata-decoded RTF \objdata at offset 0x680 4184 bytes