Malicious Office (OOXML) — malware analysis report

Static analysis result for SHA-256 166945b6e03a8cf3…

MALICIOUS

Office (OOXML)

15.4 KB
MD5: f2c11dc15dd41d48b94a58ffb54d5a8c SHA-1: 37638968184ed6a423efff572042bf7846e187be SHA-256: 166945b6e03a8cf3e2cc37e751344a5f57bd4cc47c70cbdd7fd396ca9eedbea6
100 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1059 Command and Scripting Interpreter T1203 Exploitation for Client Execution

The OOXML document contains a VBA macro, indicated by the 'OOXML_VBA' and 'OLE_VBA_AUTO' heuristics, which is designed to execute a payload. The 'macros.bas' script uses the 'CreateProcess' API from kernel32.dll, suggesting it's intended to launch a second-stage executable. The VBA project part was renamed to 'ppt/Mehnme.bin' to evade detection.

Heuristics 3

  • VBA project part renamed to evade filename detection high OOXML_VBA_PROJECT_RENAMED
    The VBA project is bound through the OOXML relationship/content type but its part is not named vbaProject.bin. Legitimate Office producers always emit vbaProject.bin; renaming it hides the macros from path-only scanners (observed in the SVCReady loader).
  • Auto_Open macro high OLE_VBA_AUTO
    Auto_Open macro
  • VBA project inside OOXML medium OOXML_VBA
    Document contains a VBA project — VBA macros present (project part renamed away from vbaProject.bin: ppt/Mehnme.bin)

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
macros.bas
8df9e19d36486a2480cc2b084fe776d85e26ebddcb5e3b70e66f00aa5b8f1f8e		 vba-macro oletools.olevba.extract_macros (decoded VBA source from OOXML) 6000 bytes
vbaProject_00.bin
ce1093ba979e7c1fd1548ca4b04e6265886c5b770b7961c3ea75b7f2cbff36ba		 vba-project OOXML VBA project: ppt/Mehnme.bin 38400 bytes

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