Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 25f4fd4985b31453…

MALICIOUS

RTF / .DOC

1.60 MB
MD5: 171adf976bea41ea05d4f4ae82604a8a SHA-1: 3c2c42f3141c045872c27f25bea5607f3ca2723c SHA-256: 25f4fd4985b314530d8e430d353285d449de3a1e6d642ae04db6ace0708291da
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 OLE object with high entropy, strongly indicating a hidden payload. Heuristics confirm the presence of an Equation Editor exploit related to CVE-2017-11882, which is triggered by the \objupdate directive. This exploit likely decodes and executes a second-stage payload from the embedded object data.

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 ~1667KB 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_off00002034.bin
946f8fecfc5764fab99fdd7dffcdc89e539d663dc8f5359d94f34e5a95993e67
rtf-objdata-decoded RTF \objdata at offset 0x2034 833718 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.99, consistent with packed or encrypted content.