Malicious RTF — malware analysis report

Static analysis result for SHA-256 0abb840fb1f29f5e…

MALICIOUS

RTF

1.41 MB First seen: 2020-02-04
MD5: c44bd6170f8d752d29173c7651a3e66d SHA-1: 2d663e9836c94bf15a8c0e5d9864f204d3bc27d9 SHA-256: 0abb840fb1f29f5eeb54fe90a6f62a39ca83c4ef4f78ef3cdb5031324aba5700
222 Risk Score

Malware Insights

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

The RTF file contains an embedded OLE object related to Equation Editor, specifically triggering CVE-2017-11882. This exploit is known to download and execute a second-stage payload. The presence of a large, high-entropy OLE object further supports the likelihood of a hidden executable payload being dropped.

Heuristics 6

  • Split hex Equation Editor ProgID + OLE object critical CVE likely 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.
  • 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.
  • \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 ~1483KB 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_off0000006c.bin rtf-objdata-decoded RTF \objdata at offset 0x6C 741582 bytes
SHA-256: ffa365eca8631f220bd1994e75c712789ad845cf8f235d6ad9de538bedd14c86
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.99, consistent with packed or encrypted content.