Malicious RTF — malware analysis report

Static analysis result for SHA-256 6437307b4fa41ff2…

MALICIOUS

RTF

49.8 KB Created: 2021-09-14 17:22:00 First seen: 2021-09-22
MD5: cfbd879663042cb00d20ce9cd3f2cb85 SHA-1: 8789cf6c934b23aa4fc176b2085e47bf8d8ce548 SHA-256: 6437307b4fa41ff21aac0f3ba1de26ee73b1839c8f915e08222c14a29bdff5ad
222 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1059.007 JavaScript

The RTF file contains OLE object data and triggers heuristics related to CVE-2017-0199 and composite monikers, indicating an exploit attempt. The embedded URLs suggest the file attempts to download a second-stage payload from the IP address 192.168.51.108. The exploit likely leverages a script, possibly JavaScript, to achieve execution.

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://192.168.51.108/side.html}{ In RTF body
    • http://192.168.51.108/side.htmlIn RTF body
    • http://192.168.51.108/side.html%In RTF body
    • http://192.168.51.108/side.html����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_off000029f4.bin rtf-objdata-decoded RTF \objdata at offset 0x29F4 3113 bytes
SHA-256: 586ac4fc97939820381da14c4abfe60d6e313724b83235b6b5409f9d18b4a4b4

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