Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 f7016f13d829a686…

MALICIOUS

RTF / .DOC

1.22 MB
MD5: df215d0397de28f29eb6ba7d58d127bb SHA-1: 5a660d05468c03314b8110a0e55fb97bb98bd58a SHA-256: f7016f13d829a686624bb855186dab2a706cbd5e12c08ceb3889d543e25548ff
222 Risk Score

Malware Insights

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

The RTF document contains an OLE object specifically identified as related to CVE-2017-11882, a known vulnerability in Microsoft Equation Editor. The presence of large, high-entropy hex-encoded data within the OLE object strongly suggests it is used to hide and deliver a secondary payload. The ".objupdate" directive further indicates an attempt to automatically activate the embedded object, facilitating exploitation.

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 ~1276KB 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_off00000074.bin
eafc4243e8efbced1089ab29a93ac9527a38b5715cdc99fe6c6d83d3c0e4cdd3
rtf-objdata-decoded RTF \objdata at offset 0x74 638516 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.99, consistent with packed or encrypted content.