PJLMON.DLL
PJL Language monitor file version info
Library on Windows 2 known copies with hashes
Is it the real PJLMON.DLL?
Installed in
C:\Windows\system32\DriverStore\FileRepository\ntprint.inf_amd64_311ad0065d69f772\Amd64\C:\Windows\system32\DriverStore\FileRepository\ntprint.inf_x86_311ad0065d69f772\I386\Signed byMicrosoft Windows
ProductMicrosoft Windows Operating System, Microsoft Corporation
DescriptionPJL Language monitor
2 known copies
10.0.19041.264 (WinBuild.160101.0800) · C:\Windows\system32\DriverStore\FileRepository\ntprint.inf_amd64_311ad0065d69f772\Amd64\PJLMON.DLL · signed by Microsoft Windows
07d4a82cccba9a1c44d6a0538a770b4ee2f97dfdf27ef4eabd3eff7a2d564bfc10.0.19041.264 (WinBuild.160101.0800) · C:\Windows\system32\DriverStore\FileRepository\ntprint.inf_x86_311ad0065d69f772\I386\PJLMON.DLL · signed by Microsoft Windows
866ef1d53b5d27d8040879bf2b3733ca7c667b0d07fa2baeeb3412d285fb23b2From 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.