Malicious Office (OOXML) — malware analysis report

Static analysis result for SHA-256 66ddbdfe9328d6a3…

MALICIOUS

Office (OOXML)

27.1 KB Created: 2021-07-15 04:24:00 UTC Authoring application: Microsoft Office Word 15.0000 First seen: 2021-11-22
MD5: 6af2470805fe10cf881871a6babf9986 SHA-1: 8cf54a1e81d1fe1ac31fa42ede46a6599a9d9dd8 SHA-256: 66ddbdfe9328d6a3f49abbb814252617fce0e05934ceeef9813e8bd30385fe50
142 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The sample is an OOXML document that exploits CVE-2023-36884 by referencing an external RTF object. This external object is hosted at HtTps://behr.ppinewsagency.live/5098/1/1069/2/0/0/0/m/files-3607001e/file.rtf. The exploitation of this CVE indicates an attempt to execute arbitrary code, likely to download and run 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://behr.ppinewsagency.live/5098/1/1069/2/0/0/0/m/files-3607001e/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 In document text (OOXML body / shared strings)
    • http://schemas.openxmlformats.org/markup-compatibility/2006In document text (OOXML body / shared strings)
    • http://schemas.openxmlformats.org/officeDocument/2006/relationshipsIn document text (OOXML body / shared strings)
    • http://schemas.openxmlformats.org/officeDocument/2006/mathIn document text (OOXML body / shared strings)
    • http://schemas.microsoft.com/office/word/2010/wordprocessingDrawingIn document text (OOXML body / shared strings)
    • http://schemas.openxmlformats.org/drawingml/2006/wordprocessingDrawingIn document text (OOXML body / shared strings)
    • http://schemas.openxmlformats.org/wordprocessingml/2006/mainIn document text (OOXML body / shared strings)
    • http://schemas.microsoft.com/office/word/2010/wordmlIn document text (OOXML body / shared strings)
    • http://schemas.microsoft.com/office/word/2012/wordmlIn document text (OOXML body / shared strings)
    • http://schemas.microsoft.com/office/word/2010/wordprocessingGroupIn document text (OOXML body / shared strings)
    • http://schemas.microsoft.com/office/word/2010/wordprocessingInkIn document text (OOXML body / shared strings)
    • http://schemas.microsoft.com/office/word/2006/wordmlIn document text (OOXML body / shared strings)
    • http://schemas.microsoft.com/office/word/2010/wordprocessingShapeIn document text (OOXML body / shared strings)
    • http://schemas.openxmlformats.org/officedocument/2006/relationships/oleobjectIn document text (OOXML body / shared strings)

Extracted artifacts 1

Files carved from inside the sample during analysis.

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