Malicious RTF — malware analysis report

Static analysis result for SHA-256 4eb760fc5ffb293c…

MALICIOUS

RTF

102.0 KB Created: 2019-06-13 02:57:00 First seen: 2019-08-04
MD5: 631f70e71fc0b3170069e3a9b2e51b47 SHA-1: bb0d114862b66100bd958b4d83a8bd739e10217b SHA-256: 4eb760fc5ffb293cffe8cef0c9b2495a334057ffa2ef50b2cbc5fbfcb6f8800d
142 Risk Score

Malware Insights

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

The RTF file contains multiple embedded OLE objects and triggers an OLE activation via \objupdate, which is a strong indicator of exploitation. The critical heuristic firing for CVE-2017-8759 confirms the exploitation of this specific vulnerability to achieve code execution. The embedded benign URL is not considered a malicious IOC.

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_off00002b47.bin rtf-objdata-decoded RTF \objdata at offset 0x2B47 20027 bytes
SHA-256: e71685c7b03c1a1efc628ae664020dd6ab624018d3967793fb67431bbe8cc329

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