Did you just download a file that is digitally signed by Intel Corporation and wonder if the file is safe? If that's the case, please read on.
You will probably see Intel Corporation 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 digital signature details for Intel Corporation with the following procedure:
Here's a screengrab of a file digitally signed by Intel Corporation:
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 Intel Corporation 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 Intel Corporation, such as the street name, city and country.
VeriSign Class 3 Code Signing 2004 CA, COMODO RSA Extended Validation Code Signing CA, VeriSign Class 3 Code Signing 2010 CA, COMODO RSA Code Signing CA and Sectigo Public Code Signing CA R36 has issued the Intel Corporation certificates. You can also examine the details of the issuer by clicking the View Certificate button shown in the screenshot above.
These are the Intel Corporation files I've gathered, thanks to the FreeFixer users.
The FreeFixer tool treats files from Intel Corporation as trusted, which means that the Intel Corporation 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 Intel Corporation file(s). I'm pretty sure those detections are incorrect and that the files are safe. It is unlikely that Intel Corporation would ship a malware file.
Detection Ratio | File Name |
---|---|
1/47 | igfxtray.exe |
1/51 | hkcmd.exe |
1/51 | igfxtray.exe |
1/50 | UNS.exe |
1/70 | xtuservice.exe |
2/56 | hkcmd.exe |
1/49 | igfxtray.exe |
1/57 | iusb3mon.exe |
2/67 | IntelSoftwareAssetManagerService.exe |
1/50 | igfxtray.exe |
1/43 | igfxtray.exe |
2/68 | IntelSoftwareAssetManagerService.exe |
1/47 | igfxtray.exe |
1/43 | igfxsrvc.exe |
1/52 | igfxtray.exe |
1/43 | setup.exe |
1/42 | igfxsrvc.exe |
1/53 | igfxtray.exe |
1/56 | LMS.exe |
1/56 | UNS.exe |
2/72 | IntelSoftwareAssetManagerService.exe |
1/51 | Accesor.dll |
1/48 | hkcmd.exe |
1/42 | igfxtray.exe |
1/47 | igfxtray.exe |
1/43 | hkcmd.exe |
1/50 | igfxsrvc.exe |
1/57 | uns.exe |
1/52 | igfxtray.exe |
1/55 | igfxtray.exe |
1/55 | hkcmd.exe |
1/55 | igfxsrvc.exe |
1/50 | igfxpers.exe |
1/62 | hkcmd.exe |
1/70 | xtuservice.exe |
1/69 | Intel-Driver-and-Support-Assistant-Installer.exe |
1/66 | xtuservice.exe |
0/49 | IAStorDataMgrSvc.exe |
0/53 | igfxtray.exe |
0/51 | IAStorIcon.exe |
0/40 | IAStorUI.exe |
0/46 | PIconStartup.exe |
0/49 | igfxtray.exe |
0/48 | igfxpers.exe |
0/47 | iusb3mon.exe |
0/50 | hkcmd.exe |
0/51 | igfxtray.exe |
Here is the detection names for the Intel Corporation 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 Intel Corporation would ship a malware file.
Scanner | Detection Names |
---|---|
AegisLab | Troj.UnPacker.Gen.lqKD |
Antiy-AVL | Trojan/Generic.ASMalwS.31149B4 |
Bkav | W32.Clod019.Trojan.ea61, W32.HfsAdware.72CF, HW32.Laneul.gwqu, W32.HfsAdware.9801 |
ByteHero | Trojan.Malware.Win32.xPack.m |
CMC | Trojan.Win32.Menti!O |
ClamAV | Win.Trojan.Agent-218686, Win.Worm.Chir-1905, Win.Worm.Chir-854 |
Cybereason | malicious.040cbd, malicious.137813, malicious.e6e1fc |
Cylance | Unsafe |
Emsisoft | Gen:Trojan.Heur.az1a4CG6jlmG (B) |
Ikarus | Virus.Win32.Madang |
Jiangmin | Trojan.PSW.Python.ac, Trojan/Menti.zuv |
TheHacker | Trojan/Menti.mtze, Trojan/Menti.mxuv, Trojan/Menti.mtwu, Trojan/Menti.mtyk, Trojan/Menti.nodl, Trojan/Menti.mvcy, Trojan/Genome.aewtk, Trojan/Menti.mxxt |
VBA32 | Trojan.Python |
Zillya | Trojan.KeyLogger.Script.1 |
The detection percentage is based on the fact that I've collected 80904 scan results for the Intel Corporation files. 41 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 done on certificates with the following serial numbers: