Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 158491653a0ddaa4…

MALICIOUS

RTF / .DOC

249.8 KB
MD5: f583c8b85b8a66f89af5b27024377acc SHA-1: 53fc98f36a3581a4312a19b2f8084486aab43a4a SHA-256: 158491653a0ddaa4369ec680ab2fc40cbf7621d900b980747bd87bdf794d63bf
202 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The sample is an RTF document that contains an embedded OLE object, specifically identified as a Microsoft Equation Editor exploit (CVE-2017-11882). This exploit is designed to decode and execute a PE file, which is likely a secondary payload. The presence of the Equation Editor exploit strongly indicates a malicious intent to compromise the user's system.

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.
  • 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_off00000041.bin
81bf7a8ec7c6ca0fb6f89e87586cbaa8f6a915053204bbbefce1a482ba085fa9
rtf-objdata-decoded RTF \objdata at offset 0x41 127809 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 8.00, consistent with packed or encrypted content.