CmdID / Files

wdi.dll

Windows Diagnostic Infrastructure file version info

Library on Windows 2 known copies with hashes 1 Sigma rule names it

Is it the real wdi.dll?

file version info and known copies

Installed inC:\Windows\system32\
C:\Windows\SysWOW64\

Signed byMicrosoft Windows

ProductMicrosoft Windows Operating System, Microsoft Corporation

DescriptionWindows Diagnostic Infrastructure

2 known copies

10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\wdi.dll · signed by Microsoft Windows

SHA-256404dda0bdf9a6c1c61653cf7e965f504b3a3a3b662f88c906aaa19a9c3df160cSHA-13b394e93ef206d30fafbf3202a5a63a4b6667580MD57d326b235ab064ff70376f1d015cc084

10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\wdi.dll · signed by Microsoft Windows

SHA-2564662064205bec0db7b10f1412e0a09a6e5e3b16de443aef7f79aca3ace24a51dSHA-1e6250b2107824b4398ae408925c10b7af9799c99MD5bb37af6e45e0f69222e057a74b4afe1e

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, "<hash>".whatis() says which known copy an MD5, SHA-1 or SHA-256 is.

What detects it

Sigma rules that name wdi.dll

When it is loaded

highPotential System DLL Sideloading From Non System LocationsNasreddine Bencherchali (Nextron Systems)

CmdID evaluates Sigma’s process creation rules against a command line. These watch what a command line does not show: a library or a driver loading, a file written, the registry, another process opened, event logs. They are listed as Sigma has them, at SigmaHQ.