Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 c0258497ad1af861…

MALICIOUS

RTF / .DOC

97.3 KB First seen: 2023-07-10
MD5: adcf92ae5e6f6d06a8539ddd2956623c SHA-1: 271ac555c4109f2c6190e3056edfeff9a41b1ae0 SHA-256: c0258497ad1af8619e82c38f659dc62dc5ef0b6d5c097671b9892f12fe753d3c
120 Risk Score

Malware Insights

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

The sample is an RTF document that contains OLE object data and triggers an object update, indicating it is designed to exploit vulnerabilities. Specifically, the RTF_EQUATION_EDITOR heuristic firing points to a known exploit targeting the Equation Editor component. This suggests the file is a malicious document intended to deliver a payload via an OLE object exploit.

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_off00001d9e.bin
b7ff233f277fbb7be6fd46306f84c669f3565afe51f412b93708382086d82a9f
rtf-objdata-decoded RTF \objdata at offset 0x1D9E 27184 bytes