Malicious RTF — malware analysis report

Static analysis result for SHA-256 38c7a0e07f930916…

MALICIOUS

RTF

3.1 KB First seen: 2018-10-19
MD5: 33e6397dbbd2770a002e1a15e7068234 SHA-1: 64192be2f86b22ba2d4fc14a1ca64e9a08d925b3 SHA-256: 38c7a0e07f9309161e1cc7b25f1cdc2d882a294edd96bc18618e43e000ad36c4
200 Risk Score

Malware Insights

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

The RTF document contains an embedded OLE object specifically identified as related to CVE-2017-11882, which is a known vulnerability in Microsoft Equation Editor. The presence of `RTF_EQUATION_EDITOR` and `CVE_2017_11882_ACTIVATION_RELATED` heuristics strongly indicates exploitation of this vulnerability. This technique is commonly used to deliver a secondary payload, hence the inclusion of Spearphishing Attachment as an initial access vector.

Heuristics 6

  • 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.
  • 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.
  • \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
  • 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 1

Files carved from inside the sample during analysis.

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