Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 50f92605317f2516…

MALICIOUS

RTF / .DOC

370.4 KB
MD5: 2f2390fffaf5a680c1cff81689f06186 SHA-1: 36d3a9fb187e4eaa85cc4d70905a0cf587291d3e SHA-256: 50f92605317f2516371d95b0cc1db1f362bc6994ec1c7f1607ea82bc79a1f57a
182 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1068 Commonly Used Port

The sample is an RTF document that leverages CVE-2017-11882, as indicated by the critical heuristic firings for RTF_EQUATION_EDITOR and CVE_2017_11882_RELATED. The presence of a high-entropy PE file carved from the OLE object data (objdata_00_off00001d6f.bin) suggests a second-stage payload is delivered via the Equation Editor exploit. The document body consists of obfuscated or garbage text, likely used to bypass simple static filters or to confuse the analyst.

Heuristics 5

  • Equation Editor OLE1 native payload — CVE-2017-11882 related critical CVE related CVE_2017_11882_RELATED
    RTF decodes to an OLE1 Equation.3 embedded object whose native data is large and payload-like, and \objupdate requests automatic activation. This is the delivery shape used by Equation Editor RCE documents such as CVE-2017-11882/CVE-2018-0802, but the malformed MTEF record needed for exact attribution was not recovered.
  • Decoded Equation Editor payload + PE critical RTF_EQUATION_EDITOR
    RTF decodes to an Equation Editor ProgID adjacent to OLE activation and the same decoded object stream contains embedded PE bytes. This matches the Equation Editor exploit surface used by CVE-2017-11882 / CVE-2018-0802 documents, while requiring payload evidence to avoid flagging benign Equation references.
  • \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 info 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_off00001d6f.bin
76f885f75d4a0d7459baa7c4457762a045ee86a32b3b226233554a122829d6fa
rtf-objdata-decoded RTF \objdata at offset 0x1D6F 185808 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 8.00, consistent with packed or encrypted content.