Did you just find a file that is digitally signed by VMware, Inc.? If so, please read on.
You will probably see VMware, Inc. when double-clicking to run the file. The publisher name shows up as the "Verified publisher" in the UAC dialog as the screencap shows:
You can view the additional details from the VMware, Inc. digital signature with the following steps:
Here's a screenshot of a file that has been digitally signed by VMware, Inc.:
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 VMware, Inc. and that the file has not been tampered with.
If you click the View Certificate button shown in the screenshot 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, and so on. You can also examine the address for VMware, Inc., such as the street name, city and country.
VeriSign Class 3 Code Signing 2004 CA, VeriSign Class 3 Code Signing 2009-2 CA, VeriSign Class 3 Code Signing 2010 CA and DigiCert Assured ID Code Signing CA-1 has issued the VMware, Inc. certificates. You can also view the details of the issuer by clicking the View Certificate button shown in the screenshot above.
These are the VMware, Inc. files I've collected, thanks to the FreeFixer users.
The FreeFixer tool treats files from VMware, Inc. as trusted, which means that the VMware, Inc. files will appear with a green background and that there is 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 VMware, Inc. file(s). My guess is that those detections are false positives and that the files are safe. It is unlikely that VMware, Inc. would ship a malware file.
Detection Ratio | File Name |
---|---|
1/36 | VMwareTray.exe |
1/36 | VMwareUser.exe |
1/47 | vmnat.exe |
1/62 | vsocklib.dll |
1/43 | vmnat.exe |
1/43 | vmnat.exe |
1/56 | vmtoolsd.exe |
1/50 | vsocklib.dll |
1/69 | vmware-usbarbitrator64.exe |
0/46 | vsocklib.dll |
0/46 | vsocklib.dll |
0/55 | vsocklib.dll |
0/50 | vsocklib.dll |
0/65 | vsocklib.dll |
0/47 | vsocklib.dll |
0/55 | vsocklib.dll |
0/57 | vsocklib.dll |
0/48 | vsocklib.dll |
0/48 | vsocklib.dll |
Here is the detection names for the VMware, Inc. 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 VMware, Inc. would ship a malware file.
Scanner | Detection Names |
---|---|
APEX | Malicious |
ByteHero | Trojan.Malware.Win32.xPack.m |
CMC | Trojan.Win32.Injects!O |
Emsisoft | Gen:Variant.Adware.Graftor.47219 (B) |
Jiangmin | Trojan/Generic.bvydo |
Prevx1 | Heuristic: Suspicious Self Modifying File |
TheHacker | Trojan/FakeMS.wq |
The detection percentage is based on the fact that I have gathered 16944 scan reports for the VMware, Inc. files. 9 of these scan results came up with some sort of detection. If you like, you can view the full details of the scan reports by examining the files listed above.
The analysis has been done on certificates with the following serial numbers: