Malicious RTF — malware analysis report

Static analysis result for SHA-256 ee1af402b06edd4c…

MALICIOUS

RTF

5.6 KB First seen: 2017-09-14
MD5: 79c29db9ed4e7af0dfb368d3f44f2e05 SHA-1: 2fba15f434fd1e17b9dc6971164277f5cad853f2 SHA-256: ee1af402b06edd4c5f51afd24401c09c6f120088604dac12a883528b2e283981
82 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF file contains an OLE object that exploits CVE-2017-0199 to fetch a remote document from http://192.168.56.1/logo.doc. This indicates the file is designed to download and execute a second-stage payload, likely leveraging the embedded OLE object for initial execution. No scripts were extracted, but the exploit itself is sufficient evidence of malicious intent.

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

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