Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 a7fe5869bb952839…

MALICIOUS

RTF / .DOC

998.1 KB
MD5: a20702f5c169b3728765437975b7ac6b SHA-1: 4283ca6ca90178f10fadaafdbb33bd2ab80e0c1c SHA-256: a7fe5869bb9528394a633e807fd21b82ede8ef47883600acedb4d6180c7d2116
262 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File

The RTF document contains multiple indicators of exploitation for CVE-2017-11882, including the presence of an Equation Editor OLE object with a high-entropy payload. The ".bin" artifact extracted from the OLE object data is likely the second-stage payload. The file's structure and exploit method strongly suggest a malicious intent to execute arbitrary code.

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 ~1021KB 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_off000000d3.bin
5e31dddb47ed78b6e78795a96df1ef1f14da24960a3c4f317980dd09306424fa
rtf-objdata-decoded RTF \objdata at offset 0xD3 510802 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 8.00, consistent with packed or encrypted content.