Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 dd0431c511137679…

MALICIOUS

RTF / .DOC

458.6 KB
MD5: 7f59fa8e66ede2de2407a2fd2c73d40c SHA-1: 5e2bdb9c3fc3b90956ddd87e3f4c6be08b314f09 SHA-256: dd0431c5111376796b2a9b8c3903deb8f80feeccda3117923d90593c8c3dfa08
202 Risk Score

Malware Insights

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

The sample is an RTF document that contains an embedded OLE object, specifically identified as related to CVE-2017-11882. This exploit is known to be used for delivering secondary payloads. The presence of the ".bin" file with high entropy further suggests it contains executable content. No document body text was available for analysis, but the critical heuristics strongly indicate an exploit attempt.

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.
  • OLE object data medium RTF_OBJDATA
    RTF contains 1 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • 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_off00000ba6.bin
f61a520da1f2bd8fde19db5fafc989c27caadb43402d0573c0998ae4087944be
rtf-objdata-decoded RTF \objdata at offset 0xBA6 233256 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 8.00, consistent with packed or encrypted content.