Malicious RTF — malware analysis report

Static analysis result for SHA-256 f8f012a9b89c3fbd…

MALICIOUS

RTF

3.5 KB First seen: 2019-05-31
MD5: 86a6ad68e803cec414db5ddb6dfe0575 SHA-1: fe160587a80db5b2db72920406fa70b5a3725426 SHA-256: f8f012a9b89c3fbdecab9b090140ba895062a66d64b90edbdb98390eaddca14f
200 Risk Score

Malware Insights

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

The RTF file contains an embedded OLE object specifically identified as an Equation Editor object, triggering heuristics for CVE-2017-11882. This exploit is known to allow for arbitrary code execution. The presence of shellcode candidate regions within the decoded object further supports this attack 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_off00000294.bin rtf-objdata-decoded RTF \objdata at offset 0x294 1439 bytes
SHA-256: 69cb7a0f297beffdfcf3c3e52adf3e40828c92370292c1ed3cd89964037c52ed
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL