Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 43e499b2e6134d8e…

MALICIOUS

RTF / .DOC

1.07 MB
MD5: 42fe2b61b0990460b5f6e228e0f9935a SHA-1: 00f55b621c69aa7436ddbc887c4deb40abb177e4 SHA-256: 43e499b2e6134d8ed1ffc5c41d6c67941e518dc627b3ff8b0f4fdc4c5dec8e75
222 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File T1059.003 Windows Command Shell

The RTF document contains an embedded OLE object with a ProgID indicative of Equation Editor, triggering the CVE-2017-11882 exploit. The presence of a large, high-entropy OLE object and the objupdate directive strongly suggest that it is designed to execute a second-stage payload. The file's structure and exploit target point to a malicious document designed for initial compromise.

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.
  • \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.
  • Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX
    RTF contains ~1123KB of hex-encoded data inside \objdata sections — may hide a payload
  • 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_off00000a4e.bin
f872ebe66cff56f6ae96e28629840215ba5366a65d2791393b2285e209a3c3dc
rtf-objdata-decoded RTF \objdata at offset 0xA4E 562000 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 8.00, consistent with packed or encrypted content.