Malicious RTF — malware analysis report

Static analysis result for SHA-256 7238f4e5edbe0e5a…

MALICIOUS

RTF

674.3 KB First seen: 2023-03-30
MD5: e24e51ec170b2341ef90321640fef797 SHA-1: d6066b94968ba76864f930eda55267549eae7f9c SHA-256: 7238f4e5edbe0e5a2242d8780fb58c47e7d32bf2c4f860c88c511c30675d0857
200 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF document contains multiple heuristics indicating the exploitation of CVE-2017-11882 through an embedded Equation Editor object. The embedded object is designed to trigger OLE activation and execute malicious code. The presence of 'Equation.3' as a ProgID strongly suggests this exploit vector. The decoded object data contains obfuscated JavaScript that likely downloads and executes a second-stage payload.

Heuristics 6

  • Equation Editor activation — CVE-2017-11882 related high CVE related CVE_2017_11882_ACTIVATION_RELATED
    RTF decodes to an Equation.3 ProgID and requests OLE activation with \objemb plus \objupdate. This reaches the legacy Equation Editor attack surface used by CVE-2017-11882/CVE-2018-0802 documents, but the malformed MTEF/native payload needed for stronger 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.
  • \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 3 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • 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 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000001a.bin
160d53e0d9e87fdb156e5eb6a04c78424e98c3d72cc03e0c6238b2746ed0ca80
rtf-objdata-decoded RTF \objdata at offset 0x1A 343496 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 1 shell/COM execution token(s).
objdata_01_off000a7bd9.bin
6ef048de06e9c2e6b420e78a489e52123766b08549a074a5f95b98ffe8558f38
rtf-objdata-decoded RTF \objdata at offset 0xA7BD9 1709 bytes
objdata_02_off000a7be9.bin
8935eb605040753f89379b3f05c2cdaefba833ec64299ed9c258020f4c1217b0
rtf-objdata-decoded RTF \objdata at offset 0xA7BE9 36 bytes