Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 5b535c36958568c9…

MALICIOUS

RTF / .DOC

1.37 MB
MD5: 24189b85b98aa717fc69697e03b96b9a SHA-1: f980749755a1f09ae5782b698da097871b37ffa4 SHA-256: 5b535c36958568c9226db768eca93aafb3b0b80e41018cc10ad5d42dd188c4ec
222 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF document contains embedded OLE object data, specifically related to the Equation Editor. Critical heuristics indicate the presence of a payload associated with CVE-2017-11882, which is known to be exploited for client execution. The large amount of hex-encoded data likely hides the malicious payload, which is then activated via an \objupdate directive.

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