Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 fcde1a9f1b5ebaac…

MALICIOUS

RTF / .DOC

639.2 KB
MD5: 8e6d90f75e321a2a164fcb417dfce456 SHA-1: a5210f5280396d3fe9b98262c00b94c5b111d2a6 SHA-256: fcde1a9f1b5ebaaca80704a3b8b1de31bcea199cb1e935748c5e87a7264cd948
100 Risk Score

Malware Insights

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

The sample is an RTF document containing embedded OLE objects, with heuristics indicating that ".objupdate" forces OLE activation. The document body text provides a lure about financial auditing to encourage users to "enable editing", which is a common tactic for macro-based malware. The presence of embedded OLE objects and the lure strongly suggest the document is designed to execute malicious code upon user interaction.

Heuristics 4

  • \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
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • 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_off00004aa4.bin
dea0ff1a4c14a599d0fdf85613045f6f511bbe53e2bb69c93805c74909e13563
rtf-objdata-decoded RTF \objdata at offset 0x4AA4 4277 bytes