Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 a02e24a057f1233f…

MALICIOUS

RTF / .DOC

998.2 KB
MD5: e3ffc99647a8f0b8a6bfba688d06ee7a SHA-1: 790233360b828a65516f7a75d594906a076f7d5d SHA-256: a02e24a057f1233f3f996a2b9aac0335ff1ce316b3391603aef7f888c0054745
222 Risk Score

Malware Insights

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

The RTF document contains an embedded OLE object specifically related to Equation Editor, strongly indicating exploitation of CVE-2017-11882. The object's data is highly entropic and large, suggesting it hides a second-stage payload. No document body or scripts were extracted, but the presence of the exploit is sufficient for a high-confidence assessment.

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