Malicious RTF — malware analysis report

Static analysis result for SHA-256 2e6ef22c57c174ea…

MALICIOUS

RTF

45.6 KB First seen: 2023-07-07
MD5: c11126e9450b2d9e8717182e077f26ac SHA-1: 1302c35b1e3adb88bcef1ec31740eb9e6041ad72 SHA-256: 2e6ef22c57c174ea7852589c043de677c11890d4d8b84c963b62455fa76f94b7
180 Risk Score

Malware Insights

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

The RTF document contains an embedded OLE object with a split Equation Editor ProgID, a known vulnerability (CVE-2017-11882). The 'SE_ENABLE_LURE' heuristic indicates the document instructs the user to enable editing, which is a common tactic to bypass security measures and trigger the exploit. The embedded OLE object is the primary indicator of a potential exploit execution.

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.
  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • \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_off0000596d.bin
3754d6b64c2051f998b4697a15d81c4ded4060d8d99714c06ee50ba110a8a206
rtf-objdata-decoded RTF \objdata at offset 0x596D 1952 bytes