Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 aa2229fc859b09da…

MALICIOUS

RTF / .DOC

1.29 MB
MD5: a3a6960a78aba71fef29813f58888abc SHA-1: 2147509b785968b61c98c2fb3ac79575b0fd4b39 SHA-256: aa2229fc859b09da4ce6977a48ef63190c42d3ad2b3399ee925826a073694eea
222 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF document contains embedded OLE objects specifically crafted to exploit the Equation Editor vulnerability (CVE-2017-11882). The presence of `RTF_EQUATION_EDITOR`, `CVE_2017_11882_RELATED`, and `RTF_OBJUPDATE` heuristics strongly indicates this attack vector. The large, high-entropy embedded data within the OLE object is characteristic of a shellcode payload designed to achieve remote code execution upon document opening.

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 ~1351KB 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_off000000b8.bin
ae13e4166403fc4c67deb9b85898dfc7e270bc7c9e2af65d37adb8343121396d
rtf-objdata-decoded RTF \objdata at offset 0xB8 675727 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 8.00, consistent with packed or encrypted content.