Malicious RTF — malware analysis report

Static analysis result for SHA-256 4d1d192d3fc81912…

MALICIOUS

RTF

3.97 MB First seen: 2020-08-10
MD5: a4141ad2c26f471a8bd1307638540258 SHA-1: 9faebd816f99cac6a41c8243aea7368bec78b19f SHA-256: 4d1d192d3fc819129bae76c4ce58f5c2309688214d0efacffa5b020a41674495
262 Risk Score

Malware Insights

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

The RTF file contains an OLE object that is highly indicative of the CVE-2017-11882 vulnerability in Microsoft Equation Editor. This vulnerability allows for the execution of arbitrary code when the object is activated, likely leading to the download and execution of a secondary payload. The presence of a large, high-entropy OLE object further supports this conclusion.

Heuristics 7

  • 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.
  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • \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 ~4157KB 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_off00000070.bin rtf-objdata-decoded RTF \objdata at offset 0x70 2078893 bytes
SHA-256: 407a90e90744b8ca7fb7dc62b1874263ff03767170beb9126f10665c06f599a4
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.99, consistent with packed or encrypted content.