DevicePairing.dll
Shell extensions for Device Pairing file version info
Library on Windows 2 known copies with hashes 1 Sigma rule names it
Is it the real DevicePairing.dll?
C:\Windows\system32\C:\Windows\SysWOW64\2 known copies
10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\DevicePairing.dll · signed by Microsoft Windows
a1da333fe0696939837f82f902f54e94f8bff8296039f2461644e1aafe87b48510.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\DevicePairing.dll · signed by Microsoft Windows
fc8e3a0d28c61dd4ba5b81a9a2fc05b0dcf65148dced315007bf4a8eecadeef8From 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.
What detects it
Sigma names DevicePairing.dll in 1 rule, for every kind of event; none is a process creation rule CmdID evaluates, so none is listed.