Malicious RTF — malware analysis report

Static analysis result for SHA-256 12ccfe2181dbfa15…

MALICIOUS

RTF

15.3 KB First seen: 2022-10-06
MD5: 3d207aeadca2c728aa5fbc8fe117162d SHA-1: f146af6c31f5d6d0e2f917c63be062b8c15931db SHA-256: 12ccfe2181dbfa15c0d272ad0e44c6e62875db0f5b9bab0d0f6cb98da774744c
140 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1204.002 Malicious Link: Malicious File T1566 Phishing T1566.001 Phishing: Spearphishing Attachment T1566.002 Phishing: Spearphishing via Service

The file is an RTF document containing an embedded OLE object, specifically targeting the Equation Editor vulnerability. The presence of the \objupdate directive indicates an attempt to automatically activate this object. The document also contains a lure instructing the user to enable editing, a common social engineering tactic to bypass security measures and execute embedded malicious content.

Heuristics 4

  • Split hex Equation Editor ProgID + OLE object critical RTF_EQUATION_EDITOR
    RTF embeds the Equation.3 ProgID as hex bytes near OLE object activation and splits the byte stream with whitespace or an ignorable RTF group. This is an Equation Editor OLE activation surface commonly used by CVE-2017-11882 / CVE-2018-0802 exploit documents.
  • \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_off00001150.bin
4ded23c3c4d83977b48e231a5bed73fd44b9e0686ce15fdb58f712bec6ae35fd
rtf-objdata-decoded RTF \objdata at offset 0x1150 1706 bytes