nltest.exe
Microsoft Logon Server Test Utility file version info
Program on Windows 15 known copies with hashes 9 Sigma rules name it
Is it the real nltest.exe?
nltestrk.exe in the file’s header: a renamed copy still carries itC:\Windows\system32\C:\Windows\SysWOW64\15 known copies
10.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\nltest.exe · signed by Microsoft Windows
f40c2711925df928fcc3cce781296922741b3b585b71e41fc9faa4404bd3c5e710.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\nltest.exe · signed by Microsoft Windows
171202183676b30c00b4d25438e64c565978b7dcf0dfc17a2f1990a237e7c11b10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\nltest.exe · signed by Microsoft Windows
214215c05ca777417c9adb9862cb40aafe66cbadf85e838e8318a2064793afd410.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\nltest.exe · signed by Microsoft Windows
a0ab27588baa72c13f1bdd3a59cc6b76b1c9789ef9e30f0b8bef968316be77b510.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\nltest.exe · signed by Microsoft Windows
7fadd9db73f868040413c2b0466c9f4898372224e83c712f3a7a1494b8f6699210.0.17763.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\nltest.exe · signed by Microsoft Windows
246aabcefcf3d661d6966fcbf09e70d6f0862aa51b696990331d073a3693f5f610.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\nltest.exe · signed by Microsoft Windows
4e8aa26ad71243d13f7ec156c31acbf1a0f1041303570e4e5cb910cc6d99056710.0.17763.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\nltest.exe · signed by Microsoft Windows
67667be06e369fd7b62328bfe70de34c34b40c2fa5837a8d241d59b37822ecc110.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\nltest.exe · signed by Microsoft Windows
7dc93701dfdafc68c810d73924c7b4074b60d0ad1da90643d7def903836a0d3710.0.17763.1 (WinBuild.160101.0800) · C:\windows\system32\nltest.exe · signed by Microsoft Windows
84ac73561a97a8d5ea4be2b817f9a0033c4a827a1e935f21aa703f040934db3b10.0.17763.1 (WinBuild.160101.0800) · C:\windows\SysWOW64\nltest.exe · signed by Microsoft Windows
f9a6cf4eb628c0c62c9c709975f21f7a249322ed6b0943825a5c49458e8e133810.0.14393.0 (rs1_release.160715-1616) · C:\Windows\SysWOW64\nltest.exe · signed by Microsoft Windows
d9cd21bea4ef9ebb9bca97bf60bede70a20ced63a3f0300fb1e35c7b2d1a8df610.0.14393.0 (rs1_release.160715-1616) · C:\Windows\system32\nltest.exe · signed by Microsoft Windows
e796f7d2d7d94c4cc3bf86fa39477ba37fcf4cb8fef3dd0161da6da2c58f60776.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\system32\nltest.exe · not signed
03ad844d4fb53d807e2d440a088e77ff3329f8817565cf097d06ac269e711bff6.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\SysWOW64\nltest.exe · not signed
9f7be873d8f6efbfe909056a69f3d83f48f6e585ba0ecef7066d45817868b967From 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.