Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 23add7ace4e76093…

MALICIOUS

RTF / .DOC

4.59 MB
MD5: 7e51798b2099b3d4fa5aa09567036ff6 SHA-1: ff384c8951bc5bab3bc2524cdf5752080b33a825 SHA-256: 23add7ace4e76093f438fa8df4de7af055f20a6fe89fbb6815b47f92df283aa1
262 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File T1027 Obfuscated Files or Information

The RTF document contains multiple indicators of malicious activity, including OLE objects and specific heuristics pointing to the Equation Editor vulnerability (CVE-2017-11882). The presence of a large, high-entropy OLE object suggests it is hiding a second-stage payload. The attack pattern is consistent with exploiting this known vulnerability to achieve initial execution.

Heuristics 7

  • 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.
  • Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX
    RTF contains ~4616KB 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_off00000095.bin
5995c680e7ba0fc2dd467a2f05b8ca13c45719a71ee68e536ab457073ace2961
rtf-objdata-decoded RTF \objdata at offset 0x95 2330825 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.97, consistent with packed or encrypted content.