Malicious RTF — malware analysis report

Static analysis result for SHA-256 359f43bfa6127371…

MALICIOUS

RTF

5.6 KB First seen: 2019-05-16
MD5: 0019606e71cb74c168875b2bc8cf1d6b SHA-1: 0f26c4758afd6e18f28144f827c39f038bf54bec SHA-256: 359f43bfa6127371891402cf77e7df0e6eb9801a73af4cc05874c04d2ae2ad6b
222 Risk Score

Malware Insights

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

The RTF file contains embedded OLE object data and is configured to automatically link and update an OLE object. This functionality is leveraged to exploit CVE-2017-0199, which allows for the remote retrieval and execution of a secondary document from the URL http://45.76.170.48/logo.doc. This indicates a likely initial access vector via spearphishing attachment, leading to the execution of a malicious payload.

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://45.76.170.48/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_off000001a2.bin rtf-objdata-decoded RTF \objdata at offset 0x1A2 2601 bytes
SHA-256: 183511532b027992d4b00b7a29f2728097a77c94662462888f72d474b14bf421

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