Malicious RTF — malware analysis report

Static analysis result for SHA-256 a4ab58cc18771c71…

MALICIOUS

RTF

11.3 KB
MD5: 6d238a412f808d2c4c56865d7f4c4d16 SHA-1: cf2c952dd7303167d7e666763dcf278088190f52 SHA-256: a4ab58cc18771c7141e96d45714b7aeb046ff7173ec5266f08da7b28d411744e
120 Risk Score

Malware Insights

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

The sample is an RTF document that contains an embedded OLE object with a split Equation Editor ProgID, indicating exploitation of CVE-2017-11882. The ".objupdate" directive forces the OLE object to activate, triggering the exploit. This technique is commonly used to download and execute a second-stage payload. No specific family could be identified, but the attack pattern is consistent with a malicious document dropper.

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_off00001675.bin
55cd20dd5b4c2c04864ecf6cb14bb256d8ea4002f86a8a687beac5e990985a7d
rtf-objdata-decoded RTF \objdata at offset 0x1675 1777 bytes