Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 1e1d729f7271e2b4…

MALICIOUS

RTF / .DOC

11.9 KB
MD5: 53052249948ce32f03385dc4b4d9ca69 SHA-1: 1f402d0f2137be58992b00cff699e73584cec08b SHA-256: 1e1d729f7271e2b488e103a904e7e1640619486bbca6605a9843f93f7e9b1302
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data and is configured to automatically update and activate these objects. This strongly suggests the document is designed to exploit OLE vulnerabilities or to embed and launch malicious content. While no specific payload or URL was directly extracted, the heuristic firings indicate a high likelihood of a malicious OLE-based attack. The document body is heavily obfuscated and does not provide clear textual clues.

Heuristics 3

  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • \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_off00001c4e.bin
32339b2c0625252b4d3fa3b4ffc7f8459cc299712db9eb68d0438b4134dc318b
rtf-objdata-decoded RTF \objdata at offset 0x1C4E 1857 bytes