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

Static analysis result for SHA-256 e1ae44d26899969d…

MALICIOUS

Office (OOXML) / .DOC

143.7 KB Created: 2023-11-28 16:43:00 UTC Authoring application: Microsoft Office Word 15.0000
MD5: 423e150d91edc568546f0d2f064a8bf1 SHA-1: d65c2f100acd9f42138661ee3620ff51471b4e1a SHA-256: e1ae44d26899969d520789e23c777d6c07785da23454664ad12b2783946a617c
140 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File: User Execution T1566.001 Phishing: Spearphishing Attachment

The sample leverages OOXML external OLE object relationships, specifically targeting CVE-2017-8759 and CVE-2023-36884. It attempts to load an external RTF file from the URL https://mofa-gov-pk.donwloaded.com/CG/016424/file.rtf. This indicates a likely delivery mechanism for a secondary payload, exploiting known vulnerabilities in Microsoft Office to achieve remote code execution.

Heuristics 4

  • CVE-2023-36884 — external RTF auto-load relationship critical CVE likely CVE_2023_36884
    Document auto-load relationship references a remote RTF file (https://mofa-gov-pk.donwloaded.com/CG/016424/file.rtf), matching the stronger Storm-0978/RomCom external-RTF delivery shape. Plain clickable hyperlinks are not enough for this CVE rule.
  • OOXML OLE2Link remote document — CVE-2017-8759 related high CVE related CVE_2017_8759_RELATED
    Document contains an o:OLEObject Type=Link whose external oleObject relationship fetches a remote Office-looking document. That is the OOXML OLE2Link staging shape used by CVE-2017-8759 campaigns when the remote document/WSDL supplies the SOAP moniker payload; the local file alone does not contain the WSDL body needed for an exact match.
  • 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.
  • 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://schemas.microsoft.com/office/word/2010/wordprocessingCanvas
    • http://schemas.openxmlformats.org/markup-compatibility/2006
    • 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/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.