Malicious RTF — malware analysis report

Static analysis result for SHA-256 a6390123d117d97f…

MALICIOUS

RTF

63.4 KB Created: 2016-11-27 22:42:00 First seen: 2019-04-18
MD5: 680c11a6848f0a99456c7d51a3659591 SHA-1: 61749b8f4adddf5fc0a31404c3adfd434e6ee800 SHA-256: a6390123d117d97f56470db59f755648dd86031664d5defc15e1376ae1b3a0e7
122 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF file contains an OLE object that leverages CVE-2017-0199 to fetch a remote template document from http://95.141.38.110/mo/dnr/tmp/template.doc. This indicates an attempt to download and execute a secondary payload. The document body content appears to be unrelated military training material, likely a lure.

Heuristics 4

  • 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.
  • 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.
  • 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://185.168.186.36/up/dnr/scan/ In RTF body
    • http://95.141.38.110/mo/dnr/tmp/template.docIn 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_off00009ca3.bin rtf-objdata-decoded RTF \objdata at offset 0x9CA3 2724 bytes
SHA-256: 5d5735ecbc809d70c2089946302aa0991f6c582148ba3a504a216a4d5e39bce7