Malicious RTF — malware analysis report

Static analysis result for SHA-256 a13cdb3f4e5b0188…

MALICIOUS

RTF

261.2 KB Created: 2018-07-03 09:28:00 First seen: 2019-01-11
MD5: 5e8ba8ab07102479754a1e14af24dfa6 SHA-1: bae5b5496f3ac143beb06dc8a88015e556c72b0e SHA-256: a13cdb3f4e5b01886e443adfb4775406ad06e4cfd09c3a010ec0e03ac6b85c27
262 Risk Score

Malware Insights

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

The RTF file contains embedded OLE objects and triggers critical heuristics for CVE-2017-11882 and CVE-2017-8759, indicating exploitation for client execution. The embedded URL suggests a download of a second-stage payload, likely an MSI installer.

Heuristics 7

  • CVE-2017-11882 — Equation Editor FONT record overflow critical CVE likely CVE_2017_11882
    Equation Editor MTEF contains an overlong FONT typeface field, the vulnerable copy primitive for CVE-2017-11882. This is stronger evidence than the Equation Editor CLSID alone because it identifies the malformed record that drives code execution in EQNEDT32.EXE.
  • 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.
  • ClamAV: Doc.Exploit.Cve_2017_11882-7570663-1 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Doc.Exploit.Cve_2017_11882-7570663-1
  • \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://rus-fishing.com/images/main/2/1/qooqsx.msi In RTF body
    • http://schemas.microsoft.com/office/word/2003/wordmlIn RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000bf6b.bin rtf-objdata-decoded RTF \objdata at offset 0xBF6B 15672 bytes
SHA-256: d9203d7d5b66c7f46ee69de17f3d7bf58510ce30c8e9000da079ac5a7440dead

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