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

Static analysis result for SHA-256 c212ef2473a886e0…

MALICIOUS

Office (OOXML) / .DOCX

50.6 KB Created: 2020-04-01 04:07:00 UTC Authoring application: Microsoft Office Word 16.0000
MD5: 9a34fb61528295256a15c1c99ff6bd19 SHA-1: 1d81c2a56835337496c8787df11dd344852293d0 SHA-256: c212ef2473a886e0bd18d88177fdc266f5a2ef20be35675eeca489fde2c42da2
120 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File

The sample is a malicious OOXML document that leverages CVE-2023-36884 to load a remote RTF template. The heuristic firings indicate an external relationship to 'http://office-cloud-reserve.com/Scan.rtf?raw=true', which is likely the source of a secondary payload. No scripts were extracted, but the exploit itself is the primary attack vector.

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 (http://office-cloud-reserve.com/Scan.rtf?raw=true), matching the stronger Storm-0978/RomCom external-RTF delivery shape. Plain clickable hyperlinks are not enough for this CVE rule.
  • Remote template injection high OOXML_REMOTE_TEMPLATE
    Document references a remote template URL (http://office-cloud-reserve.com/Scan.rtf?raw=true) — a common remote-template-injection vector used by Hancitor, Emotet and many phishing campaigns. Word can fetch and apply the remote template; macros in that template may execute depending on Office policy and trust state.
  • External relationship medium OOXML_EXTERNAL_REL
    External target in word/_rels/settings.xml.rels: http://office-cloud-reserve.com/Scan.rtf?raw=true
  • 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.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/2016/wordml/cid
    • 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.