Malicious RTF — malware analysis report

Static analysis result for SHA-256 3a3edc50681f9418…

MALICIOUS

RTF

89.7 KB First seen: 2019-08-04
MD5: 6454df7d5bbeb38168a0c9704a408aa9 SHA-1: 63b3fe8aab7e9659b981041b22b90b6df1bbacee SHA-256: 3a3edc50681f94181bbfa042678394b6ee9ee6271793daa7b7a6f7d095618598
140 Risk Score

Malware Insights

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

The RTF file contains an embedded OLE object with a split Equation Editor ProgID, indicating exploitation of a known vulnerability. The presence of `\objupdate` further suggests forced activation of this object. The extracted artifact `objdata_00_off000079b3.bin` is likely the shellcode payload responsible for executing arbitrary 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 1 \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_off000079b3.bin rtf-objdata-decoded RTF \objdata at offset 0x79B3 1567 bytes
SHA-256: a0ef88dd69fa77376f0e40d5bf12d5fa37bac640351d6e80e84299d4153de46d
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL