Malicious Office (OOXML) — malware analysis report

Static analysis result for SHA-256 d44eabf2325e17a5…

MALICIOUS

Office (OOXML)

41.8 KB Created: 2021-06-22 12:43:05 UTC Authoring application: Microsoft Excel 16.0300
MD5: c5f69384472e7a0bddb2f9aae16700a9 SHA-1: 139a4647a937bd6079a3baf47b55037bd038c503 SHA-256: d44eabf2325e17a5cd70b3ec68f348b6c6964f3e00caa1ecbdbd44f6fc57adac
260 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1059.001 PowerShell T1218.011 System Binary Proxy Execution: Rundll32

The file is an Office document containing VBA macros. The Workbook_Open macro is present and references cmd.exe and PowerShell, indicating an attempt to execute external commands. Specifically, the VBA code uses WMI to launch a process, which is a common technique for downloading and executing further malicious payloads. The presence of a Base64 decoding function suggests obfuscation of the payload.

Heuristics 6

  • PowerShell reference in VBA critical OLE_VBA_PS
    PowerShell reference in VBA
  • VBA WMI Win32_Process launcher critical OLE_VBA_WMI_PROCESS_CREATE
    VBA macro builds or references a WMI moniker for Win32_Process and invokes .Create to start a command. This is a high-confidence macro execution chain that often hides the WMI class name through string concatenation or helper functions.
  • Workbook_Open macro high OLE_VBA_WBOPEN
    Workbook_Open macro
  • GetObject call high OLE_VBA_GETOBJ
    GetObject call
  • cmd.exe reference in VBA high OLE_VBA_CMD
    cmd.exe reference in VBA
  • VBA project inside OOXML medium OOXML_VBA
    Document contains a VBA project — VBA macros present

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
macros.bas
a56f44fa3b6c9b9eb5158bc3b2b21766cd33888f58200ca92f34b0dca8c3e97c
vba-macro oletools.olevba.extract_macros (decoded VBA source from OOXML) 35430 bytes
vbaProject_00.bin
dbdf80a455b54f9a461933d3a7956ee63652919175fbcb86adfc7776065b3bc7
vba-project OOXML VBA project: xl/vbaProject.bin 11776 bytes