Malicious RTF — malware analysis report

Static analysis result for SHA-256 e941cb8053e33408…

MALICIOUS

RTF

65.4 KB Created: 2019-01-31 15:55:00 First seen: 2019-05-16
MD5: eb743d017081bc084252d34e3cff830e SHA-1: ea3640ec9402a9cfeccbc3b653497156989bb663 SHA-256: e941cb8053e334085c654dc029d7611f01969f1424f1a9c6f46bd421fac457fe
182 Risk Score

Malware Insights

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

The RTF file contains an OLE object that exploits CVE-2017-0199, a known vulnerability for remote code execution. The exploit targets the URL http://192.168.187.140/logo.txt to download and likely execute a secondary payload. This indicates a malicious document designed to compromise the user's system upon opening.

Heuristics 5

  • 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.
  • 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.187.140/logo.txt 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_off00002a86.bin rtf-objdata-decoded RTF \objdata at offset 0x2A86 2601 bytes
SHA-256: bae9d5f7e0f8276467a0c0ce7039ca271aa8657f743c8a324f30c5b7a47a8f5d

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