Malicious RTF — malware analysis report

Static analysis result for SHA-256 fe7614f25878afad…

MALICIOUS

RTF

1.19 MB Created: 2019-07-14 23:43:00 First seen: 2019-11-20
MD5: a72b4bad99453f300825f2c5a2cb9ec2 SHA-1: 8d7b0dc8a41c90ae17226d6e6b40fc91a9e722a9 SHA-256: fe7614f25878afadf69bcf2c09761cc1134d99b1b03fff7051134d170ba42782
222 Risk Score

Malware Insights

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

The RTF file contains embedded OLE objects with excessive hex-encoded data, and a critical heuristic indicates exploitation of CVE-2017-8759. This suggests the file is designed to exploit this vulnerability to execute arbitrary code, likely by downloading and running a second-stage payload.

Heuristics 7

  • CVE-2017-8759 — MSXML SAX OLE activation critical CVE likely CVE_2017_8759
    RTF contains a hex-encoded OLE1 object for Msxml2.SAXXMLReader.6.0 followed by an embedded OLE compound document, and the document requests OLE activation. This matches the RTF staging shape used for CVE-2017-8759 SOAP/WSDL parser code injection.
  • \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 ~1184KB of hex-encoded data inside \objdata sections — may hide a payload
  • Suspicious extracted artifact high 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.
  • OLE object data medium RTF_OBJDATA
    RTF contains 3 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://schemas.microsoft.com/office/word/2003/wordml In RTF body

Extracted artifacts 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000028fc.bin rtf-objdata-decoded RTF \objdata at offset 0x28FC 188974 bytes
SHA-256: 4416248a1725e1be8fa2b1732431fb89e4757d7d813216ddef94b8afe5837a37
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved macro source contains an auto-exec entry point and execution/download terms.
objdata_01_off00065145.bin rtf-objdata-decoded RTF \objdata at offset 0x65145 188974 bytes
SHA-256: e91d0ba3713fa7a8dde30ddfa38d6ca611183a67f608c3fa1218a5860909d5ca
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved macro source contains an auto-exec entry point and execution/download terms.
objdata_02_off000c798e.bin rtf-objdata-decoded RTF \objdata at offset 0xC798E 188974 bytes
SHA-256: 101145e0dac39ae0753fff11db2bc897dbc3df98be26d7566b4ea52fcd10139f
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved macro source contains an auto-exec entry point and execution/download terms.