Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 ac988909e573046b…

MALICIOUS

RTF / .DOC

93.6 KB
MD5: 5c4285e236670850d7bea4b4112f3fd1 SHA-1: f3cc8a4f7904f72f5fb9fbf20898a43d480f27f4 SHA-256: ac988909e573046b5c49b787bc5e97419565882c0e27914c2c2bc48bcb2b509f
222 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1559.002 Component Object Model and Distributed Component Object Model

The RTF document contains an embedded OLE object specifically related to Equation Editor, triggering critical heuristics for CVE-2017-11882. This indicates the file is designed to exploit this known vulnerability for initial code execution. The presence of ".bin" file within the OLE object suggests a secondary payload delivery mechanism.

Heuristics 6

  • 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.
  • Split hex Equation Editor ProgID + OLE object critical 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.
  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • \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 2 \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_off00001c6b.bin
2034742a86b9736e9de4c160d9f2d105496b945365a78fe7d5f88aeec11f5422
rtf-objdata-decoded RTF \objdata at offset 0x1C6B 44102 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 8.00, consistent with packed or encrypted content.