Malicious RTF — malware analysis report

Static analysis result for SHA-256 73679b9abeef831d…

MALICIOUS

RTF

85.0 KB Created: 2014-03-28 15:13:00 First seen: 2019-05-16
MD5: 00f7d4d3359baca94f77e475c09bab6a SHA-1: 5de9b844b9c6d18c5707e42c0f4f6ab13cf7a3fd SHA-256: 73679b9abeef831d7dfe30b3445ac45e1add01814fa7b2f135aae1eec455d637
222 Risk Score

Malware Insights

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

The RTF file contains OLE object data and exhibits characteristics of CVE-2017-0199 and CVE-2017-8570, indicating it's designed to drop a script. The embedded URL, http://msk-bk-db-02:7778/forms/bk_report/EEFIMENKO/tmp_053595317985546.xls, is likely the source for a secondary payload. The document body is a service memo, a common lure for social engineering.

Heuristics 6

  • 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.
  • 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.
  • 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://msk-bk-db-02:7778/forms/bk_report/EEFIMENKO/tmp_053595317985546.xls 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_off00009573.bin rtf-objdata-decoded RTF \objdata at offset 0x9573 3113 bytes
SHA-256: efdec18bfeb1e6e4c5f7c559087f786bcca858995690eb0ef338c9301f36f3a9

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