Malicious RTF — malware analysis report

Static analysis result for SHA-256 d164cc2783de8e4b…

MALICIOUS

RTF

5.6 KB Authoring application: Msftedit 5.41.21.2510 First seen: 2018-11-13
MD5: 9599597bb634b9945debf286e71511f6 SHA-1: 3bd495ffbc17217d3d0c8873597bb03b803cca1c SHA-256: d164cc2783de8e4b3b573c819593f49d09e5a69171f8056f43ec1a9c41325a88
222 Risk Score

Malware Insights

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

The RTF file contains an OLE object that is automatically linked and updated, indicating an attempt to activate embedded content. Crucially, it exploits CVE-2017-0199 by referencing the remote URL http://192.168.72.153, which is highly indicative of a malicious payload download. This technique is commonly used in spearphishing attachments to deliver secondary malware.

Heuristics 6

  • CVE-2017-0199 (OLE2Link / remote URL Moniker) critical CVE likely CVE_2017_0199
    RTF contains a URL Moniker OLE link whose decoded target is remote. Office can fetch and process the response through the CVE-2017-0199 OLE2Link attack path, but the server-side content type is not proven statically.
  • ClamAV: Rtf.Exploit.CVE_2017_0199-6335035-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Rtf.Exploit.CVE_2017_0199-6335035-0
  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • \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 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://192.168.72.153 In RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000104.bin rtf-objdata-decoded RTF \objdata at offset 0x104 2724 bytes
SHA-256: 9bc082e59cdea79ad77ca0491e70723145d289c67b966769237cbe45f4742b81