Did you just run into a file that has a digital signature from Sysinternals? If that's the case, please read on.
You will typically notice Sysinternals when running the file. The publisher name is displayed as the "Verified publisher" in the UAC dialog as the screenshot shows:
You can view the digital signature details for Sysinternals with the following steps:
Here is a screengrab of a file digitally signed by Sysinternals:
As you can see in the screenshot above, Windows states that "This digital signature is OK". This means that the file has been published by Sysinternals and that the file has not been tampered with.
If you click the View Certificate button shown in the screengrab above, you can see all the details of the certificate, such as when it was issued, who issued the certificate, how long it is valid, etc. You can also view the address for Sysinternals, such as the street name, city and country.
VeriSign Class 3 Code Signing 2009-2 CA, VeriSign Class 3 Code Signing 2010 CA and VeriSign Class 3 Code Signing 2004 CA has issued the Sysinternals certificates. You can also view the details of the issuer by clicking the View Certificate button shown in the screenshot above.
These are the Sysinternals files I have gathered, thanks to the FreeFixer users.
The FreeFixer tool treats files from Sysinternals as safe, which means that the Sysinternals files will appear with a green background and that there's no removal checkbox for the file. However, as you can see in the scan results below, a few of the anti-virus scanners detects the Sysinternals file(s). I'm pretty sure those detections are false positives and that the files are safe. It is unlikely that Sysinternals would ship a malware file.
Detection Ratio | File Name |
---|---|
1/50 | PSEXESVC.EXE |
1/68 | PSEXESVC.exe |
0/46 | PROCEXP152.SYS |
0/47 | procexp64.exe |
0/49 | PSSDNSVC.EXE |
0/53 | procexp64.exe |
0/57 | procexp64.exe |
0/55 | PROCEXP152.SYS |
0/56 | PROCEXP64.exe |
0/56 | procexp64.exe |
0/60 | PROCEXP152.SYS |
Here is the detection names for the Sysinternals files. I've grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.
As mentioned above, I think these detections are incorrect since it is very unlikely that Sysinternals would ship a malware file.
Scanner | Detection Names |
---|---|
Sophos | PsExec, PsExec (PUA) |
The detection percentage is based on that I've collected 759 scan reports for the Sysinternals files. 2 of these scan reports came up with some sort of detection. If you like, you can view the full details of the scan results by examining the files listed above.
The analysis is based on certificates with the following serial numbers: