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

Static analysis result for SHA-256 8401b9a2fd54d965…

MALICIOUS

Office (OOXML) / .DOCX

194.4 KB Created: 2022-03-25 02:52:00 UTC Authoring application: Microsoft Office Word 16.0000
MD5: 62ac2db2f7add6b492f335137466e8a6 SHA-1: e250d5ffbc66125a4de10f05d13c435311bf16ef SHA-256: 8401b9a2fd54d9654ef55b338c056de34e026fc9990fb59bc532c8875f553827
160 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File: User Execution T1059.001 PowerShell

The document exploits CVE-2022-30190 (Follina) by embedding an external OLE object that references a malicious URL. This technique is designed to download and execute a second-stage payload. The heuristic firings and the embedded URL strongly indicate this exploit is the primary attack vector.

Heuristics 4

  • CVE-2022-30190 — Follina stage-1 external HTML oleObject critical CVE likely CVE_2022_30190
    External OLEObject relationship targets a remote .html with the Follina delivery shape (oleObject -> HTTP(S) HTML with trailing Moniker '!'). In live Follina samples the ms-msdt: trigger is served by the remote HTML, not the document itself.
  • ClamAV: Win.Exploit.CVE_2022_30190-9951234-1 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Win.Exploit.CVE_2022_30190-9951234-1
  • 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.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/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.