Malicious RTF — malware analysis report

Static analysis result for SHA-256 646758298a11c8a6…

MALICIOUS

RTF

5.6 KB First seen: 2020-05-14
MD5: 662c55bb660437dfeb2fb28af95b1d6e SHA-1: 5a6e93845621771259ac2fbc879ddd3047c19219 SHA-256: 646758298a11c8a6064ca3861305d0c473664365a517cbb754c7d1b923d2a3dc
222 Risk Score

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.56.1/logo.doc 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_off00000182.bin rtf-objdata-decoded RTF \objdata at offset 0x182 2601 bytes
SHA-256: c4bbf4cd5e0fef7949413a26bc5cab4a2c62e04af473df24a15ada3b5f07a7b7