Malicious RTF — malware analysis report

Static analysis result for SHA-256 133a113a688555c6…

MALICIOUS

RTF

429.2 KB Created: 2019-06-12 09:44:00 First seen: 2019-09-30
MD5: f2436fa1489204662f3ecf91cda05af5 SHA-1: 55e053d1060b6a7e7131055a8a166485c01a7ab7 SHA-256: 133a113a688555c63d34c56ecbe81d9d83a37d89c214968d0f553fb17e4a09cd
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 7 \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 7

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00002cdf.bin rtf-objdata-decoded RTF \objdata at offset 0x2CDF 16955 bytes
SHA-256: d02b905b420b923d2b212ff6ddf2a8ad36efafd0abe390f360e68ce76461371e
objdata_01_off00010ac8.bin rtf-objdata-decoded RTF \objdata at offset 0x10AC8 16955 bytes
SHA-256: ef8b98c577b1346b982d5f17024817961fdd244fe81f501b27c74d4f65b4d3cc
objdata_02_off0001e8b1.bin rtf-objdata-decoded RTF \objdata at offset 0x1E8B1 16955 bytes
SHA-256: 6d5de6fdd4a997d356d298610d0f0d3ad694062a18ae46f9c88e5c74148c2a55
objdata_03_off0002c69a.bin rtf-objdata-decoded RTF \objdata at offset 0x2C69A 16955 bytes
SHA-256: f3e1fe02e2d0b48a40d184a5b93a18012facd27893b0b7d061e4260f545f660c
objdata_04_off0003a483.bin rtf-objdata-decoded RTF \objdata at offset 0x3A483 16955 bytes
SHA-256: 3a5cbd6d16954770f012e44a30aa2649780200fe73852317fb32c7ac06b4b372
objdata_05_off0004826c.bin rtf-objdata-decoded RTF \objdata at offset 0x4826C 16955 bytes
SHA-256: 5ecd5095dcafea5785c4d8bed15e4b40706d8446aaece707d77c351eb34d33af
objdata_06_off00056055.bin rtf-objdata-decoded RTF \objdata at offset 0x56055 16955 bytes
SHA-256: b392054adee9cd2ea05c38e74db38df941a67210ec556188acca8ac975cfe28f

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