Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 2cbb598180eeb778…

MALICIOUS

RTF / .DOC

21.4 KB First seen: 2021-09-17
MD5: 1ea45982f10a9a53d2f87a5630ca99b5 SHA-1: 810e5fb603572c6d46ffc530f347ba5e53f5d3a0 SHA-256: 2cbb598180eeb778aed295e9108b8ad47d8700d70abb4421a8531918efb726df
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 is configured to automatically update and activate these objects. This indicates an attempt to exploit OLE vulnerabilities to execute embedded code. While no specific script or payload was directly extracted, the heuristics strongly suggest a malicious OLE object is embedded, designed to trigger on opening. The document body is heavily obfuscated and does not provide clear textual lures.

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_off00000f54.bin
eb0d62d88e89c63df8de083b1894fc4dba2ac471224611a5201ecb37f53c308d
rtf-objdata-decoded RTF \objdata at offset 0xF54 1721 bytes