Malicious RTF — malware analysis report

Static analysis result for SHA-256 60590f533566af92…

MALICIOUS

RTF

2.9 KB First seen: 2021-05-22
MD5: 9533f04d7fbc8d4a8aab7b6de4f09e2b SHA-1: 549b6411b7c3c356876bed8f78c360bc0386cd2c SHA-256: 60590f533566af921c1693646be8c4fdb763ebd4fe588301f98da2dbeaf097f6
140 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 heuristics for the Equation Editor vulnerability. This indicates the file is designed to exploit a known vulnerability to achieve arbitrary code execution upon opening. The embedded artifact 'objdata_00_off000000ed.bin' is likely the payload or exploit code.

Heuristics 4

  • 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 2 \objdata section(s) — embedded OLE objects
  • Suspicious extracted artifact medium EXTRACTED_FILE_STATIC_TRIAGE
    One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000000ed.bin rtf-objdata-decoded RTF \objdata at offset 0xED 1271 bytes
SHA-256: db025c8b9fd029a012af3a51b02484f48aa9c60e1a1475e5b6087f0854278a44
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL