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

Static analysis result for SHA-256 eeeb99f94029fd36…

MALICIOUS

Office (OOXML) / .DOC

12.3 KB Created: 2022-02-04 12:37:00 UTC Authoring application: Microsoft Office Word 15.0000
MD5: 466fb005506e1dc15118a6768b2c7e5a SHA-1: 34fdaf8593013d0f4569439f7891017703f0c294 SHA-256: eeeb99f94029fd366dcde7da2a75a849833c5f5932d8f1412a89ca15b9e9ebb7
140 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File T1566.001 Spearphishing Attachment

The sample is an OOXML document that leverages external OLE objects to load remote content. Specifically, it exploits CVE-2017-8759 and CVE-2023-36884, indicated by heuristic firings, to fetch and execute an RTF file from the URL https://dgmp-paknavy.mod-pk.com/14325/1/10/2/0/0/0/m/files-5291bef6/file.rtf. The document body appears to be a benign-looking official memo, likely a lure.

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://dgmp-paknavy.mod-pk.com/14325/1/10/2/0/0/0/m/files-5291bef6/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.openxml
    • 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

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
emf_00.emf
1833637d2bb49186e0667ae0896ecc4d5b00b3383529f74edb75cad8748cd9b3		 ooxml-emf OOXML EMF part: word/media/image1.emf 52 bytes

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