Malicious RTF — malware analysis report

Static analysis result for SHA-256 754a1711edc6228b…

MALICIOUS

RTF

5.6 KB Authoring application: Msftedit 5.41.21.2510 First seen: 2019-04-18
MD5: 79709a5890dfb1432978b247f3f75b90 SHA-1: b7449248b233a867d3e3639aef0f5fdeb1367250 SHA-256: 754a1711edc6228ba9fd29b1baddae2ff634e6f5a66de0a0107a72bf9f52d89a
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, which is known to download and execute remote content. The embedded URL points to a local IP address, suggesting a controlled environment or internal testing, but the exploit mechanism is clear. The file is identified as malicious by ClamAV with a signature specific to this CVE.

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.2.111:8080// 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: 6940d16c61afe0eaf56ea39237b67c8267d58d06d991dfe5563b2fdf27b38bf8

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