Did you just stumble upon a file that has been digitally signed by McAfee, Inc.? If so, please read on.
You will probably see McAfee, Inc. when clicking to run the file. The publisher name is displayed as the "Verified publisher" in the UAC dialog as the screenshot shows:
You can view the additional details from the McAfee, Inc. digital signature with the following procedure:
Here is a screenshot of a file signed by McAfee, Inc.:
As you can see in the screenshot above, Windows states that "This digital signature is OK". This implies that the file has been published by McAfee, Inc. and that the file has not been tampered with.
If you click the View Certificate button shown in the screenshot above, you can view 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 McAfee, Inc., such as the street name, city and country.
VeriSign Class 3 Code Signing 2010 CA, VeriSign Class 3 Code Signing 2004 CA and Symantec Class 3 SHA256 Code Signing CA has issued the McAfee, Inc. certificates. You can also examine the details of the issuer by clicking the View Certificate button shown in the screencap above.
These are the McAfee, Inc. files I have collected, thanks to the FreeFixer users.
The FreeFixer tool treats files from McAfee, Inc. as trusted, which means that the McAfee, Inc. 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 McAfee, Inc. file(s). I'm pretty sure those detections are incorrect and that the files are safe. It is unlikely that McAfee, Inc. would ship a malware file.
Detection Ratio | File Name |
---|---|
1/53 | McAfeeMSS_IE.dll |
1/49 | McAfeeMSS_IE.dll |
1/54 | mfevtps.exe |
1/56 | upgrade.exe |
2/67 | native_proxy.exe |
1/54 | mfevtps.exe |
1/56 | mccatupdate.dll |
2/56 | UninstallPEF.exe |
1/61 | 010344~1.exe |
1/62 | 018999~1.exe |
1/55 | McVsMap.exe |
1/57 | SHSTAT.EXE |
1/54 | Zu_.exe |
1/56 | 0008911458334047mcinst.exe |
1/53 | 51392B95-99C7-4ECE-9AE5-C939E660B4B8 |
1/55 | 017862~1.exe |
1/66 | Un_A.exe |
1/52 | SHSTAT.EXE |
2/46 | 024618~1.exe |
1/40 | proxyver.dll |
1/51 | mfevtps.exe |
1/54 | RaptorClient.exe |
1/56 | 015725~1.exe |
1/55 | mfevtps.exe |
1/51 | mfevtps.exe |
1/56 | GetSusp.exe |
1/57 | mcagent.exe |
1/43 | McProxy.exe |
1/56 | Au_.exe |
1/56 | upgrade.exe |
1/56 | 0195381467129857mcinst.exe |
1/68 | 0281271510290273mcinst.exe |
1/68 | mcdatrep.exe |
0/52 | SSScheduler.exe |
0/57 | saPlugin.dll |
0/57 | PEFService.exe |
0/68 | DADUpdater.exe |
0/52 | mfevtps.exe |
0/54 | RealProtect.exe |
0/55 | mfemms.exe |
0/44 | MCCTXM~1.DLL |
0/49 | McSvHost.exe |
Here's the detection names for the McAfee, 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 false positives since it is very unlikely that McAfee, Inc. would ship a malware file.
Scanner | Detection Names |
---|---|
AegisLab | W32.Kate, Gen.Variant.Kazy!c |
Antiy-AVL | Trojan/Win32.SGeneric, Trojan/Win32.Rozena |
Baidu | Win32.Trojan.WisdomEyes.16070401.9500.9848 |
Bkav | W32.HfsAdware.F87D, HW32.Packed.8BF3 |
ByteHero | Trojan.Malware.Win32.xPack.m |
CMC | Trojan.Win32.VBKrypt!O |
Cybereason | malicious.3a8528 |
DrWeb | DLOADER.Trojan, BACKDOOR.Trojan |
Ikarus | not-a-virus:AdWare.Yotoon |
NANO-Antivirus | Riskware.Nsis.Adware.dpjqgk |
Rising | PE:Malware.BetterSurf!6.11BF |
Sunbelt | Bulk Trojan |
TrendMicro-HouseCall | Suspici.E263CDF9, TROJ_GEN.F47V1205 |
eSafe | Win32.Trojan |
The detection percentage is based on that I've collected 58051 scan results for the McAfee, Inc. files. 36 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: