Malicious RTF — malware analysis report

Static analysis result for SHA-256 f90b04bfb2a9fc9c…

MALICIOUS

RTF

371.8 KB Created: 2019-06-19 02:39:00 First seen: 2019-08-04
MD5: cf7139c8298d2eb579e0ee1d593621b8 SHA-1: ec6a2c12d371d67b8c5a46ba99728e514f2fb6a7 SHA-256: f90b04bfb2a9fc9c5db660edaf2390d8c8549da32f9dfef70b40df027cc03de0
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 6 \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 6

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00002925.bin rtf-objdata-decoded RTF \objdata at offset 0x2925 17985 bytes
SHA-256: 42b845de32f0e6c8a45731ebcb6be369ce239f9127e3c2f120f0b704bded9c1c
objdata_01_off00010ceb.bin rtf-objdata-decoded RTF \objdata at offset 0x10CEB 17985 bytes
SHA-256: 19842e22a1aa6929b1190c51b8671f6aa871fba886e68a9cc47b94ff38649023
objdata_02_off0001f0af.bin rtf-objdata-decoded RTF \objdata at offset 0x1F0AF 17985 bytes
SHA-256: 477fea807210ff2461e2df1b8e29cecdd80623a57608a2099c93c67136096850
objdata_03_off0002d473.bin rtf-objdata-decoded RTF \objdata at offset 0x2D473 17985 bytes
SHA-256: ea19c92eb8c554fc6580344954db3ba497574f2669299384c55c071b8e2f9835
objdata_04_off0003b837.bin rtf-objdata-decoded RTF \objdata at offset 0x3B837 17985 bytes
SHA-256: 2a6ff8765abe1b9f9fae63a617e11ef7ec95fbbfbc72d1164a548598b1e8e538
objdata_05_off00049bfb.bin rtf-objdata-decoded RTF \objdata at offset 0x49BFB 17985 bytes
SHA-256: 8dca2786dfba5bac028e828ae8d4eccf1ccce954e7b849c0b1bfbe30356d7728

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