Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 322ee27d075262f4…

MALICIOUS

RTF / .DOC

34.2 KB First seen: 2023-04-12
MD5: 67cd2049820b2d82a3f010e733ae6160 SHA-1: c303afe05821aea5a55db518d5234f805effdb96 SHA-256: 322ee27d075262f479e99ceeea59f61e018a502cf6a8573e21c9493547312a75
160 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File

The RTF document contains an embedded OLE object and specifically targets the Equation Editor, a known vector for exploits like CVE-2017-11882. The presence of ` tf_objupdate` and `SE_ENABLE_LURE` heuristics indicates the document is designed to trick the user into activating the object, which would then likely trigger the exploit. No specific malware family could be identified from the available evidence.

Heuristics 5

  • 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
  • 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_off000056e5.bin
c4095c77115b7c1611af4675407446330d83368238aa23a9d9d75a8bf0565e1c
rtf-objdata-decoded RTF \objdata at offset 0x56E5 1842 bytes