Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 f40201743250cd62…

MALICIOUS

RTF / .DOC

740.7 KB
MD5: f26bb424ef01ec203239aa3a6856faca SHA-1: 43368a01d4d0842df97c91a2aa09975f0f90a3e9 SHA-256: f40201743250cd62b21ea6a53c9b5cac0cbe8e7eb36b4b899321a63e5ab589ac
120 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1566.001 Spearphishing Attachment T1059.005 Visual Basic

The sample is an RTF document containing OLE object data and an embedded OLE object that is automatically linked and updated, indicating an attempt to execute embedded content. The document body contains a lure instructing the user to 'enable editing' and mentions financial statements and auditors, suggesting a pretext to bypass security measures. The heuristic SE_ENABLE_LURE confirms this social engineering tactic. The presence of OLE object manipulation suggests the document is designed to download and execute a secondary 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_off00021181.bin
12fd5d5a2896dca91c385941d72dee27b03f65ed785fc119bd179d574e3e378a
rtf-objdata-decoded RTF \objdata at offset 0x21181 4242 bytes