Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 24cda86f6fee49b4…

MALICIOUS

RTF / .DOC

3.90 MB
MD5: 96b755d193cbfe19fd0be015f3766fda SHA-1: dbc77a0c991e0f57add7dcb2d1b01c56e01dee67 SHA-256: 24cda86f6fee49b4116cbd7907440ca4662332304b68be8a3cadc7daa9d95941
222 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. Heuristics indicate that this object is a decoded Equation Editor payload, specifically related to CVE-2017-11882. This exploit is known to deliver a secondary payload, which in this case is likely a PE file. No document body text was available for analysis, but the presence of the Equation Editor exploit strongly suggests an attack pattern focused on exploiting software vulnerabilities for initial execution.

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.
  • Decoded Equation Editor payload + PE critical RTF_EQUATION_EDITOR
    RTF decodes to an Equation Editor ProgID adjacent to OLE activation and the same decoded object stream contains embedded PE bytes. This matches the Equation Editor exploit surface used by CVE-2017-11882 / CVE-2018-0802 documents, while requiring payload evidence to avoid flagging benign Equation references.
  • \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 ~4083KB of hex-encoded data inside \objdata sections — may hide a payload
  • OLE object data medium RTF_OBJDATA
    RTF contains 1 \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_off000018a1.bin
1d0a860824345b3fb9fc2e9276f960ed3736e3f7948379de5f6c8dda822ce5f3
rtf-objdata-decoded RTF \objdata at offset 0x18A1 2041908 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 8.00, consistent with packed or encrypted content.