Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 e8900527d096a241…

MALICIOUS

RTF / .DOC

12.3 KB
MD5: 33372052195ced200428aa0895930c8c SHA-1: 544997ed35dc95b879ec5742143f87b81b3f2b03 SHA-256: e8900527d096a2413297a7d028018f8d60a0d5f5734e7940740a038bf0538f37
60 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Phishing: Spearphishing Attachment T1059.001 Command and Scripting Interpreter: PowerShell T1204.002 Malicious File: User Execution: Malicious File

The sample is an RTF document that contains embedded OLE objects, indicated by the RTF_OBJDATA heuristic. The RTF_OBJUPDATE heuristic suggests that these objects are designed to be activated automatically, which is a common technique for exploiting vulnerabilities or delivering malicious content. The document body is heavily obfuscated and does not provide clear textual clues about its intent. Given the heuristics, the likely attack pattern involves exploiting the OLE object mechanism to execute arbitrary code, potentially downloading and running a secondary payload.

Heuristics 2

  • \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_off00001a79.bin
a0a45f5baf4da1e99807e9bf76a0285a69da91ef751558c634b4a608eec748c0
rtf-objdata-decoded RTF \objdata at offset 0x1A79 1799 bytes