Malicious RTF — malware analysis report

Static analysis result for SHA-256 86f9c33378a2665c…

MALICIOUS

RTF

88.4 KB First seen: 2024-08-21
MD5: 85485a1e88e7a07db924b5e3ac587c52 SHA-1: 675d08c2fc31ef344b23f5c8552c2b850a1b3dca SHA-256: 86f9c33378a2665c897d3fec71b4605d647282a699e672dd62c7e009ba6f5f5a
120 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious File Execution T1566 Phishing T1059.001 PowerShell

The sample is an RTF document that contains an embedded OLE object, specifically targeting the Equation Editor vulnerability. The ".objupdate" directive indicates that the embedded object will be activated automatically upon opening the document. This is a common technique for exploiting vulnerabilities like CVE-2017-11882 to achieve arbitrary code execution, likely to download and run a secondary payload.

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_off00001352.bin
2b7559574ff22d06b9382ba49a199d0116b872a2bd01f502cf4c73c3faa24524
rtf-objdata-decoded RTF \objdata at offset 0x1352 1836 bytes