Malicious Office (OOXML) / .DOC — malware analysis report

Heuristics 7

• CVE-2017-0199 (OLE2Link / remote URL Moniker) critical CVE likely CVE_2017_0199
  (in altChunk RTF word/afchunk.rtf) 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.
• altChunk imports embedded RTF (RTF injection) critical OOXML_ALTCHUNK_RTF
  Document inlines an embedded RTF via an aFChunk relationship and a <w:altChunk> body element. This is the canonical RTF-injection wrapper used to smuggle RTF exploits (Equation Editor / URL Moniker / objdata) past DOCX-only scanners. Word opens the wrapper and executes the RTF inline. Recursing into the RTF for the exact exploit primitive.
• 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
  (in altChunk RTF word/afchunk.rtf) 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
  (in altChunk RTF word/afchunk.rtf) 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
  (in altChunk RTF word/afchunk.rtf) RTF contains 2 \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://74.50.94.156/MSHTML_C7/start.xml

  • http://schemas.openxmlformats.org/drawingml/2006/main
  • http://schemas.openxmlformats.org/drawingml/2006/picture
  • http://schemas.microsoft.com/office/word/2010/wordprocessingCanvas
  • http://schemas.microsoft.com/office/drawing/2014/chartex
  • http://schemas.microsoft.com/office/drawing/2015/9/8/chartex
  • http://schemas.microsoft.com/office/drawing/2015/10/21/chartex
  • http://schemas.microsoft.com/office/drawing/2016/5/9/chartex
  • http://schemas.microsoft.com/office/drawing/2016/5/10/chartex
  • http://schemas.microsoft.com/office/drawing/2016/5/11/chartex
  • http://schemas.microsoft.com/office/drawing/2016/5/12/chartex
  • http://schemas.microsoft.com/office/drawing/2016/5/13/chartex
  • http://schemas.microsoft.com/office/drawing/2016/5/14/chartex
  • http://schemas.openxmlformats.org/markup-compatibility/2006
  • http://schemas.microsoft.com/office/drawing/2016/ink
  • http://schemas.microsoft.com/office/drawing/2017/model3d
  • http://schemas.openxmlformats.org/officeDocument/2006/relationships
  • http://schemas.openxmlformats.org/officeDocument/2006/math
  • http://schemas.microsoft.com/office/word/2010/wordprocessingDrawing
  • http://schemas.openxmlformats.org/drawingml/2006/wordprocessingDrawing
  • http://schemas.openxmlformats.org/wordprocessingml/2006/main
  • http://schemas.microsoft.com/office/word/2010/wordml
  • http://schemas.microsoft.com/office/word/2012/wordml
  • http://schemas.microsoft.com/office/word/2018/wordml/cex
  • http://schemas.microsoft.com/office/word/2016/wordml/cid
  • http://schemas.microsoft.com/office/word/2018/wordml
  • http://schemas.microsoft.com/office/word/2020/wordml/sdtdatahash
  • http://schemas.microsoft.com/office/word/2015/wordml/symex
  • http://schemas.microsoft.com/office/word/2010/wordprocessingGroup
  • http://schemas.microsoft.com/office/word/2010/wordprocessingInk
  • http://schemas.microsoft.com/office/word/2006/wordml
  • http://schemas.microsoft.com/office/word/2010/wordprocessingShape

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