Malicious RTF — malware analysis report

Static analysis result for SHA-256 72331b4adc52117e…

MALICIOUS

RTF

263.0 KB Created: 2019-08-23 10:50:00 First seen: 2019-10-29
MD5: 403146d581ed64c97a9986bad7768347 SHA-1: 629513197c81bc3c4aaf63e3fb955d46e7244ece SHA-256: 72331b4adc52117e64b9103f0f0c4a7e20ebb171a101b5e33341cb9d91ec185b
142 Risk Score

Malware Insights

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

The RTF file contains an embedded OLE object that is configured to update automatically upon opening. This behavior, combined with the critical heuristic firing for CVE-2017-8759, indicates that the file is designed to exploit this vulnerability for client execution. The embedded URL, although benign, is associated with the OLE object's structure.

Heuristics 5

  • 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.
  • 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
  • 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 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000319fd.bin rtf-objdata-decoded RTF \objdata at offset 0x319FD 25542 bytes
SHA-256: 209513a49289a79345090cc956e08bee4f6ab6ea982d3cebc207faa7d1114ecd

Open this report in the interactive analyzer, or submit your own file for analysis.