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

Heuristics 6

• OOXML OLE2Link remote loader — CVE-2017-0199 related high CVE related CVE_2017_0199_RELATED
  Document contains an o:OLEObject Type=Link whose external oleObject relationship points to a remote URL. This is the OOXML OLE2Link activation shape associated with CVE-2017-0199 delivery, but the local file does not expose URL Moniker bytes or a weaponized extension/content type, so the exact CVE cannot be proven statically.
• Embedded Office object carries macros critical OFFICE_EMBEDDED_MACRO_OBJECT
  This document embeds a second Office file that itself contains a VBA macro project or an Excel 4.0 (XLM) macro sheet. Hiding a macro-bearing workbook or document inside another document — frequently under an obfuscated, non-standard part name — is a macro-smuggling technique that defeats scanners which only inspect the outer document's macro storage. No benign authoring workflow stages a hidden macro project this way.
• External OLE object relationship high OOXML_EXTERNAL_OLE_OBJECT
  Document contains an oleObject relationship whose target is an external HTTP(S) URL. Office resolves this through OLE/object update paths rather than as a normal user-clicked hyperlink.
• Suspicious extracted artifact high EXTRACTED_FILE_STATIC_TRIAGE
  One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.
• Embedded OLE object medium OOXML_OLE_OBJECT
  Document contains an embedded OLE object
• 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 https://www.mediafire.com/file/tli8d8xqvx6z0zz/update.doc/file

  • https://www.mediafire.com/file/6vip6utwodclo5k/1.htm/file
  • 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.microsoft.com/office/2019/extlst
  • 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.