Malicious RTF — malware analysis report

Static analysis result for SHA-256 f165dc05132dac87…

MALICIOUS

RTF

5.5 KB First seen: 2018-11-13
MD5: 775402677eb6e8c2549d3373e7c01fb4 SHA-1: 8a417539b5c860ce06e9c0668e81db6f2d676b8f SHA-256: f165dc05132dac870952c28560398f18b01c59c06f8805b4d4a60c48c93851b2
82 Risk Score

Malware Insights

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

The RTF file contains an OLE object that leverages the CVE-2017-0199 vulnerability. This vulnerability allows the embedded object to fetch and execute a remote document from the URL http://192.168.56.1/logo.doc, indicating a likely initial access vector via spearphishing attachment and exploitation for client execution.

Heuristics 3

  • 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.
  • 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_off00000116.bin rtf-objdata-decoded RTF \objdata at offset 0x116 2601 bytes
SHA-256: c4bbf4cd5e0fef7949413a26bc5cab4a2c62e04af473df24a15ada3b5f07a7b7

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