Malicious RTF — malware analysis report

Static analysis result for SHA-256 4c9355fe813be8db…

MALICIOUS

RTF

44.4 KB First seen: 2019-05-10
MD5: 02eaeed09c49e39fa5365b9d29de3ef3 SHA-1: cc7f364701dab81a75bfd084a48b5de1edff4658 SHA-256: 4c9355fe813be8db11d572aef66f7303fcf226ac052a0546fac1edff3317059b
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 that leverages a known vulnerability in the Equation Editor. This technique is commonly used to execute arbitrary code, which in turn is often used to download and run additional malicious payloads. The presence of the 'RTF_EQUATION_EDITOR' and 'RTF_OBJUPDATE' heuristics strongly indicates this exploit.

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_off0000a575.bin rtf-objdata-decoded RTF \objdata at offset 0xA575 1546 bytes
SHA-256: 283e77e341e54b63b98eda9b6a1368abe96fe0e943529917f714aa9372565b46
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL