Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 c81b5c5dc1649bf4…

MALICIOUS

RTF / .DOC

765.3 KB
MD5: 6b6a00426ea5374a952ecd5f547045f1 SHA-1: c697ffbccc370123c685ded332cbd1569a05a99b SHA-256: c81b5c5dc1649bf42b0563c5e96b255789b17652ccb63e688a3c8eef2820c1e7
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 sample is an RTF document containing OLE object data and is configured to automatically update and activate OLE objects, indicating an attempt to execute embedded content. The document body provides a lure related to financial audits, instructing the user to 'Enable editing', which is a common tactic to bypass macro security. The heuristics RTF_OBJAUTLINK and RTF_OBJUPDATE strongly suggest that the document is designed to trigger the execution of embedded malicious content upon opening.

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_off00035851.bin
d3c1a22196e1bf5d260b352f19ac6332920bec1b98adcf5b47134abf08af6011
rtf-objdata-decoded RTF \objdata at offset 0x35851 2365 bytes