CmdID / Files

xolehlp.dll

Microsoft Distributed Transaction Coordinator Helper APIs DLL file version info

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

Is it the real xolehlp.dll?

file version info and known copies

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

Signed byMicrosoft Windows

ProductMicrosoft Windows Operating System, Microsoft Corporation

DescriptionMicrosoft Distributed Transaction Coordinator Helper APIs DLL

2 known copies

2001.12.10941.16384 (WinBuild.160101.0800) · C:\Windows\system32\xolehlp.dll · signed by Microsoft Windows

SHA-2564746e1fb132157769f865dc6064ade1e3f17f0a8a7f59206c4db5224caf8eb91SHA-13799699202396cc66d02c0fd79067af887308d41MD5eb2949af144e39ffc802b4662828cafd

2001.12.10941.16384 (WinBuild.160101.0800) · C:\Windows\SysWOW64\xolehlp.dll · signed by Microsoft Windows

SHA-256e47004d2c5218a1c81ef8b2906bb5f075ba70c37f805012b27dfb296845393abSHA-193560b04009cb26c9b189c89b205281b25161307MD59c7b69fd706ba8736446e804740ca0c0

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 xolehlp.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.