Malicious RTF — malware analysis report

Static analysis result for SHA-256 1dbc190a74c9a2f2…

MALICIOUS

RTF

1.00 MB First seen: 2021-06-04
MD5: 31949990c07e29924c00b1d77a26b83d SHA-1: e06358afd379d76ffac01145b49b166806087417 SHA-256: 1dbc190a74c9a2f21f2236a7cc96add30e65f625a201dd69237638d6749d728d
222 Risk Score

Malware Insights

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

The RTF file contains OLE object data, specifically related to Equation Editor, and triggers heuristics for CVE-2017-11882. This indicates the file is designed to exploit this known vulnerability for client-side execution. The presence of OLE objects and the specific CVE association strongly suggest a malicious document intended to deliver a payload.

Heuristics 6

  • Equation Editor OLE1 native payload — CVE-2017-11882 related critical CVE related CVE_2017_11882_RELATED
    RTF decodes to an OLE1 Equation.3 embedded object whose native data is large and payload-like, and \objupdate requests automatic activation. This is the delivery shape used by Equation Editor RCE documents such as CVE-2017-11882/CVE-2018-0802, but the malformed MTEF record needed for exact attribution was not recovered.
  • 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 2 \objdata section(s) — embedded OLE objects
  • Suspicious extracted artifact info 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_off00000092.bin rtf-objdata-decoded RTF \objdata at offset 0x92 460426 bytes
SHA-256: 778004d6cd0125ed2657f6dd38c72281be528aedf27dff1b941b8c39d3f9b768
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.97, consistent with packed or encrypted content.