Malicious RTF — malware analysis report

Static analysis result for SHA-256 442fb7de37e2c9a6…

MALICIOUS

RTF

979.6 KB First seen: 2020-06-01
MD5: e820889edfdfcf3bb9f1e5c4544a269c SHA-1: 6461a6c4ef514e585286c231a829863e1ce8a127 SHA-256: 442fb7de37e2c9a6eef803a7d245eb77527da87865072e6e6118bee7ba948a22
220 Risk Score

Malware Insights

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

The RTF file contains an embedded OLE object specifically identified as related to CVE-2017-11882. This exploit is known to facilitate the execution of arbitrary code, suggesting the embedded object is a malicious payload. The presence of ".bin" in the extracted artifact name and its high entropy further support this conclusion. The file is likely delivered as a spearphishing attachment.

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.
  • 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 medium 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_off000019c9.bin rtf-objdata-decoded RTF \objdata at offset 0x19C9 498244 bytes
SHA-256: 839aa6e146fdacb26608202e31514210b73988eca7c2e4c84a5d0faeed6a12e5
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL Carved artifact entropy is 8.00, consistent with packed or encrypted content.