wbemtest.exe

WMI Test Tool file version info (xCyclopedia)

LOLBAS Execute 1 ATT&CK technique 1 documented command 6 known copies with hashes

How wbemtest.exe is abused

documented by LOLBAS

Execute T1047 Windows Management Instrumentation

Each abuse is LOLBAS's category and the options and words it uses; the full write-up is on LOLBAS's page for wbemtest.exe.

1 documented command

from LOLBAS, each read by the identifier

Execute T1047 Windows Management Instrumentation Any privileges

Execute arbitary commands through WMI through a GUI managment interface for Web Based Enterprise Management testing (WBEM). Uses WMI to Create and instance of a Win32_Process WMI class with a commandline argument of the target command to spawn. Spawns a GUI so it requires interactive access. For a demo, see link to blog in resources.

wbemtest.exe

Identify

The command the identifier reads trips no Sigma process-creation rule. These commands and their descriptions are from LOLBAS’s entry for wbemtest.exe, by saulpanders, at commit 2056cb766250 of 2026-09-26, under the GPL-3.0 and LOLBAS’s notice, with no warranty. Changed: Markdown is shown formatted. The source is in lolbas-gtfobins-commands.json.gz, and the full entry is on LOLBAS’s page for wbemtest.exe. The identifier reads it with LOLBAS’s placeholders filled in: a URL as https://example.com/file, a share as \\192.0.2.10\share\file, a path as C:\Data\file and a command as calc.exe.

What detects it

Sigma process creation rules

T1047Windows Management Instrumentation

Is it the real wbemtest.exe?

file version info and known copies

Installed inC:\Windows\system32\wbem\

Signed byMicrosoft Windows

ProductMicrosoft Windows Operating System, Microsoft Corporation

DescriptionWMI Test Tool

6 known copies

10.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\wbem\wbemtest.exe · signed by Microsoft Windows

d76895f19cb1a4b711556ef7f6c8257cd854f08d6510030b1304c3712285779c

10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\wbem\wbemtest.exe · signed by Microsoft Windows

2828d06fe31d1d3a1910dc4f370ca652f10cb0f8c83cd0ccdec1f72a1469ddb9

10.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\wbem\wbemtest.exe · signed by Microsoft Windows

c8866db117cfa76ddbbae1eaf64aa614cc73c4bdd48e315a85e2221fbbf22154

10.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\wbem\wbemtest.exe · signed by Microsoft Windows

3406b6adf7d5bf8d7b75c9761b9ba24d1daba8ee00bc5d014fe947b2dc0423a4

10.0.14393.0 (rs1_release.160715-1616) · C:\Windows\system32\wbem\wbemtest.exe · signed by Microsoft Windows

29775fc3cf0e3251181b4154157a0a2328a5c3d50f72173da7f59e8274f90db1

6.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\system32\wbem\wbemtest.exe · not signed

ed0b243f223839e41743c40ed813c8e44c07a668c4bb7b269ce4a327c92c72b8

From the file’s version info and the copies recorded by xCyclopedia (MIT). A copy in another folder, signed by someone else or with another hash is not necessarily malicious, but it is worth a closer look. In Ceplin, "<sha256>".whatis() says which known copy a hash is.