Malicious RTF — malware analysis report

Static analysis result for SHA-256 d037181a9e8d5720…

MALICIOUS

RTF

14.2 KB First seen: 2023-02-17
MD5: 8318aec68f9d4c0a09e9a23c3f66bdc3 SHA-1: 15bdd0d6897e80ec1bc80800759981b5f46d4935 SHA-256: d037181a9e8d57201e9cd772144f2ce7e7a0b87f7362ccae4e055096ff3ea9b1
120 Risk Score

Malware Insights

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

The sample is an RTF document that contains embedded OLE object data and triggers an ".objupdate" call, indicating it attempts to activate embedded objects. The critical heuristic firing for "RTF_EQUATION_EDITOR" strongly suggests exploitation of the Equation Editor vulnerability (CVE-2017-11882), which is commonly used to deliver secondary payloads. No document body or script content was available for further analysis, but the exploit itself is sufficient to infer a malicious intent to execute code.

Heuristics 3

  • 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

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001c85.bin
ccf11f8de864e18b41b0af850dd66b7a231538b66f9a6911f7ee85e06b4c8994
rtf-objdata-decoded RTF \objdata at offset 0x1C85 1603 bytes