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

Static analysis result for SHA-256 57d761453bbc6ba9…

MALICIOUS

Office (OOXML) / .DOC

255.7 KB Created: 2024-06-19 06:25:00 UTC Authoring application: Microsoft Office Word 14.0000
MD5: 872c2ddf6467b1220ee83dca0e118214 SHA-1: dbc5756895b6585527bd6ebc4411ea6a4a6e2886 SHA-256: 57d761453bbc6ba9ace467f4491d7a19b9c7e097f81d9772efbcd2f43ada4dce
140 Risk Score

Malware Insights

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

The sample is a malicious OOXML document that leverages CVE-2023-36884 and CVE-2017-8759 vulnerabilities. It attempts to load an external RTF object from the URL https://mailarmylk.mods.email/Ltr86-1aadeec4/file.rtf, indicating a likely exploit delivery mechanism. No scripts were extracted, but the heuristics strongly suggest exploitation of known vulnerabilities to download and execute a secondary payload.

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://mailarmylk.mods.email/Ltr86-1aadeec4/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/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.