Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 da7597eed278b6eb…

MALICIOUS

RTF / .DOC

513.2 KB
MD5: fb3027e4c7adc0370181f6f73c6dff33 SHA-1: 9ded925615bd1ef1c5dd88febdd10b1bb29b83df SHA-256: da7597eed278b6ebb330685e1caea6c1bc6ad9b2abff9afa05633f4cb5f7a123
120 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1204.002 Malicious Link: Malicious File T1566 Phishing T1566.001 Phishing: Spearphishing Attachment T1059 Command and Scripting Interpreter T1059.005 Command and Scripting Interpreter: Visual Basic

The RTF document contains OLE object data and is configured to automatically update and activate OLE objects, indicating an attempt to execute embedded content. The document body presents a lure related to financial audits, instructing the user to 'Enable editing', which is a common tactic to bypass macro security. The presence of `RTF_OBJAUTLINK` and `RTF_OBJUPDATE` heuristics strongly suggests that the embedded OLE object is designed to be activated, likely to download and execute a second-stage payload.

Heuristics 4

  • 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 1 \objdata section(s) — embedded OLE objects
  • Macro/content-enable lure medium SE_ENABLE_LURE
    Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00041830.bin
07c13d9afcd7ea8242cb26b67b3fd225e17ec1f7d6e465699264484577bd539d
rtf-objdata-decoded RTF \objdata at offset 0x41830 1313 bytes