Malicious RTF — malware analysis report

Static analysis result for SHA-256 52ca32d6213d87de…

MALICIOUS

RTF

18.8 KB First seen: 2020-09-07
MD5: 91f84a443b994ad5433c2d59e5869a61 SHA-1: 4546325a091dea38765b6b0a9cf0f7a9ef0dbcf9 SHA-256: 52ca32d6213d87deb4dfcd3374da42985ba8ae335de4ac9a5e80791d104d7cea
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains OLE object data and specifically triggers the RTF_EQUATION_EDITOR heuristic, indicating exploitation of the Equation Editor vulnerability. The RTF_OBJUPDATE heuristic suggests that the embedded OLE object is automatically activated, likely leading to the execution of a secondary payload. The file is classified as malicious, and the attack pattern involves exploiting this vulnerability for initial execution.

Heuristics 3

  • Split hex Equation Editor ProgID + OLE object critical CVE likely 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_off000011da.bin rtf-objdata-decoded RTF \objdata at offset 0x11DA 1742 bytes
SHA-256: 7d07564f420485d296093cddeab5d740dcfac3bffffe97c30ab6c9d82819b38c

Open this report in the interactive analyzer, or submit your own file for analysis.