Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 3e1ba9d9fae253f1…

MALICIOUS

RTF / .DOC

642.7 KB
MD5: b16595c7c02434cb4e95e46eaa864262 SHA-1: d9ed513e1cc6a3538c12fb404ff576c32028a3bd SHA-256: 3e1ba9d9fae253f1cebc7ddaafbc893f10cd8fd9b644e4b18f4e4f06f3cb62b0
100 Risk Score

Malware Insights

MITRE ATT&CK
T1204 User Execution: Malicious Link T1566.001 Phishing: Spearphishing Attachment

The sample is an RTF document containing embedded OLE object data, which is configured to update upon opening. The document body contains a lure instructing the user to 'Enable editing', a common tactic to bypass macro security. This suggests the embedded OLE object is intended to be activated, likely to download and execute a secondary payload.

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_off00007718.bin
3b77f4b0154979244e60f9c2e42943bdb23389478b31f524f6966d5ef07f4705
rtf-objdata-decoded RTF \objdata at offset 0x7718 4225 bytes