Malicious RTF — malware analysis report

Static analysis result for SHA-256 7248db253aaf79a6…

MALICIOUS

RTF

28.2 KB First seen: 2019-05-16
MD5: 5d659d7d6576b74f8fb565e23f8a8e7e SHA-1: 4474007f51bdd6eaae7619ac4f2da0ec446cd83f SHA-256: 7248db253aaf79a6092ac429596bab9928b1b0383b7a33141ca72817adb8f30b
262 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF file contains multiple indicators of malicious OLE object embedding and automatic linking, specifically related to CVE-2017-8570. This vulnerability is leveraged to drop and execute a script, which in turn downloads a second-stage executable from the provided URL. The embedded OLE object data and the extracted artifact suggest the execution of shellcode, likely to facilitate the download and execution of the payload.

Heuristics 8

  • Composite Moniker — CVE-2017-8570 (drops SCT script) critical CVE related CVE_2017_8570
    RTF \objdata decodes to OLE data containing the Composite Moniker — CVE-2017-8570 (drops SCT script) CLSID — the vulnerable control/moniker is embedded directly in the document's object stream, the delivery shape of this exploit. RTF objects auto-render when Word opens the file.
  • Composite Moniker in RTF OLE object high CVE related RTF_COMPOSITE_MONIKER_RELATED
    RTF contains Composite Moniker CLSID in OLE object context, but no nearby scriptlet/SCT payload was confirmed. Treat as related moniker attack-surface evidence rather than proof of CVE-2017-8570 exploitation.
  • 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.
  • Suspicious extracted artifact high EXTRACTED_FILE_STATIC_TRIAGE
    One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.
  • OLE object data medium RTF_OBJDATA
    RTF contains 2 \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://5.206.225.246/zanku.exe In RTF body

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00004fef.bin rtf-objdata-decoded RTF \objdata at offset 0x4FEF 1515 bytes
SHA-256: 4ce58a73f67ddf2284c0df0fb20751d09273f65d47bf3b9d5c9bccd00c702c8b
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis recovered command string(s): WScript.Shell")
objdata_01_off00005c0f.bin rtf-objdata-decoded RTF \objdata at offset 0x5C0F 2632 bytes
SHA-256: 1d2db3af5dabe5b27c5b0c88db97f8e45de0a02d9c685c4bb3922612d64260bd