Did you just run into a file that has a digital signature from Google Inc? If that's the case, please read on.
You will probably see Google Inc when clicking to run the file. The publisher name is displayed as the "Verified publisher" in the UAC dialog as the screencap shows:
You can view the digital signature details for Google Inc with the following steps:
Here's a screencap of a file that has been digitally signed by Google Inc:
As you can see in the screenshot above, Windows reports that "This digital signature is OK". This means that the file has been published by Google Inc and that no one has tampered with the file.
If you click the View Certificate button shown in the screenshot above, you can examine 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 examine the address for Google Inc, such as the street name, city and country.
VeriSign Class 3 Code Signing 2010 CA, Thawte Code Signing CA - G2, Thawte Code Signing CA, Symantec Class 3 SHA256 Code Signing CA, VeriSign Class 3 Code Signing 2004 CA and VeriSign Class 3 Code Signing 2009-2 CA has issued the Google Inc certificates. You can also examine the details of the issuer by clicking the View Certificate button shown in the screenshot above.
The following are the Google Inc files I have gathered, thanks to the FreeFixer users.
The FreeFixer tool treats files from Google Inc as trusted, which means that the Google 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 Google Inc file(s). My guess is that those detections are false positives and that the files are safe. It's unlikely that Google Inc would ship a malware file.
Here is the detection names for the Google Inc files. I have 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 Google Inc would ship a malware file.
Scanner | Detection Names |
---|---|
APEX | Malicious |
Acronis | malware |
AegisLab | W32.Sality, W32.Neshta |
Antiy-AVL | Trojan/Win32.SGeneric, Trojan[Downloader]/Win32.Adload, Trojan/Win32.Genome.gen, Trojan/Win32.Agent, Trojan/Win32.Llac, Trojan/Win32.Monder.gen, Trojan/Win32.Win32, Trojan/Win32.RC5_Dropper |
Baidu | Win32.Virus.Lamer.g, Win32.Trojan.WisdomEyes.16070401.9500.9936 |
BitDefender | Gen:Variant.Adware.Dropper.103 |
Bkav | W32.Clod2ba.Trojan.5b50, W32.Clod76c.Trojan.10e8, HW32.Laneul.ewqy, HW32.Stranfom.xwya, [Microsoft Visual C++ 8], W32.Clod684.Trojan.d06c, W32.HfsAdware.DF5E, W32.HfsAdware.3252, W32.HfsAdware.4792 |
ByteHero | Trojan.Malware.Win32.xPack.m, Trojan.Exception.gen.101 |
CMC | Virus.Win32.Daum!O |
ClamAV | Win.Trojan.Bancos-2115, Win.Worm.Vasor-21, WIN.Trojan.Agent-46603 |
Cylance | Unsafe |
Cyren | W32/Trojan.RNUD-4975 |
Emsisoft | Win32.Expiro.BW (B), Gen:Variant.Adware.Dropper.103 (B), Android.Trojan.GingerMaster.Q (B) |
Jiangmin | Trojan/Vilsel.kut, TrojanDownloader.Adload.tov, Packed.PolyCrypt.amql |
NANO-Antivirus | Trojan.Win32.IframeExec.cqpxcw, Trojan.Win32.Agent2.bbzyal |
Norman | HmBlocker.A |
Paloalto | generic.ml |
Rising | PE:Malware.Generic(Thunder)!1.A1C4 [F], PE:Worm.Chir!6.1232, PE:PUF.CrossRider!1.A157 [F], Malware.RDM.18!5.18, PE:Malware.XPACK/RDM!5.1 |
Tencent | Trojan.Win32.Qudamah.Gen.4, Trojan.Win32.YY.Gen.6 |
TrendMicro-HouseCall | Suspicious_GEN.F47V0809, HV_AGENT_BK083E56.TOMC, HV_AGENT_BK0838E1.TOMC, TROJ_GEN.F47V1223, Suspicious_GEN.F47V0524, Suspicious_GEN.F47V0419, Suspicious_GEN.F47V0423, Suspicious_GEN.F47V0425, Suspicious_GEN.F47V0510, Suspicious_GEN.F47V0507 |
Webroot | W32.Adware.Gen |
Zoner | Trojan.Wauchos.Q |
nProtect | Trojan/W32.Agent.81432.F |
The detection percentage is based on the fact that I've gathered 95776 scan results for the Google Inc files. 113 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: