Malicious RTF — malware analysis report

Static analysis result for SHA-256 5e55c14c69488688…

MALICIOUS

RTF

1.42 MB First seen: 2021-06-30
MD5: e7aa25c4b346064c69e2dbb3cd313cee SHA-1: 4d78bcf23ed2e5916abfd5d8f1822a29a254de3f SHA-256: 5e55c14c694886886decc0a269fca04c90ae0c525b1ea0d4f8673d67781ec940
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 designed to execute arbitrary code, likely a second-stage payload, upon activation. The presence of a large, high-entropy OLE object further supports the payload delivery mechanism.

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 ~1489KB of hex-encoded data inside \objdata sections — may hide a payload
  • OLE object data medium RTF_OBJDATA
    RTF contains 2 \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_off000000db.bin rtf-objdata-decoded RTF \objdata at offset 0xDB 745019 bytes
SHA-256: 0f80b290b7999e55e7b0a36581b9587ca6ed3cb297f1de62d94b948f171517de
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 8.00, consistent with packed or encrypted content.