Malicious RTF — malware analysis report

Static analysis result for SHA-256 715d12486a4a72da…

MALICIOUS

RTF

5.6 KB First seen: 2018-01-23
MD5: 91d7a80f8775ae141e884c437700a499 SHA-1: 22a6b4bf03e11efdc88231b5f76d6b497d56f0ab SHA-256: 715d12486a4a72da929fc2de4f31950fe2a8582f90d6dc2eb25a4bb7434bdbde
222 Risk Score

Malware Insights

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

The RTF file contains OLE object data and is configured to automatically update and activate an OLE object, indicating an attempt to exploit vulnerabilities. Specifically, the critical heuristic firing for CVE-2017-0199 points to the exploitation of a remote URL moniker vulnerability. This vulnerability is used to download and execute a secondary payload from the specified URL, http://54.91.231.141/logo.doc.

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://54.91.231.141/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: d0d78d835fc332ddc2c4a5971e97fc4e0b6b02d26a7ed8035806061339249ede

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