Symantec Corporation - 0.078% Detection Rate *
Did you just run into a file that has been digitally signed by Symantec Corporation? If so, please read on.
You'll probably notice Symantec Corporation when running the file. The publisher name shows up as the "Verified publisher" in the UAC dialog as the screenshot shows:
You can view the additional details from the Symantec Corporation digital signature with the following procedure:
- Open up Windows Explorer and locate the Symantec Corporation file
- Right-click the file and select Properties
- Click on the Digital Signatures tab
- Click on the View Certificate button
Here is a screenshot of a file signed by Symantec 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 Symantec Corporation and that the file has not been tampered with.
If you click the View Certificate button shown in the screencap 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 Symantec Corporation, 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, VeriSign Class 3 Code Signing 2001-4 CA and Symantec Class 3 SHA256 Code Signing CA has issued the Symantec Corporation certificates. You can also see the details of the issuer by clicking the View Certificate button shown in the screenshot above.
Symantec Corporation Files
These are the Symantec Corporation files I've gathered, thanks to the FreeFixer users.
The FreeFixer tool treats files from Symantec Corporation as trusted, which means that the Symantec Corporation 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 Symantec Corporation file(s). My guess is that those detections are false positives and that the files are safe. It's unlikely that Symantec Corporation would ship a malware file.
| Detection Ratio | File Name |
|---|---|
| 1/46 | syminstallstub.exe |
| 1/47 | SymInstallStub.exe |
| 1/56 | FSDUI_Custom.exe |
| 1/35 | AutoDetectPkg.exe |
| 2/51 | FixBlast.exe |
| 1/50 | aluschedulersvc.exe |
| 1/43 | SymInstallStub.exe |
| 1/46 | SymInstallStub.exe |
| 1/46 | SymInstallStub.exe |
| 2/43 | cltlmh.exe |
| 1/48 | AluSchedulerSvc.exe |
| 3/49 | Nss_IObitDel.exe |
| 1/46 | NPE (1).exe |
| 1/55 | setup.exe |
| 1/55 | NPE (1).exe |
| 2/46 | SymInstallStub.exe |
| 1/49 | coIEPlg.dll |
| 1/55 | Upgrade.exe |
| 1/48 | DWHWizrd.exe |
| 1/50 | Nss.exe |
| 1/56 | conathst.exe |
| 4/42 | IDSxpx86.dll |
| 1/48 | Nss.exe |
| 1/50 | N360.exe |
| 1/50 | GENotify.dll |
| 1/54 | Setup.exe |
| 1/57 | NPE.exe |
| 2/57 | cltLMH.exe |
| 1/57 | QBackup.dll |
| 1/57 | COMM.DLL |
| 1/61 | Nss.exe |
| 1/61 | NortonNISDownloader.exe |
| 0/56 | conathst.exe |
| 0/48 | NST.exe |
| 0/45 | ccL120U.dll |
| 0/46 | symlcbrd.sys |
| 0/57 | SEVINST64x86.EXE |
| 0/48 | NBRT-Retail-Downloader.exe |
| 0/41 | NavLogon.dll |
| 0/55 | PIFSvc.exe |
| 0/55 | coIEPlg.dll |
Scanner and Detection Names
Here's the detection names for the Symantec Corporation 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 incorrect since it is very unlikely that Symantec Corporation would ship a malware file.
| Scanner | Detection Names |
|---|---|
| AegisLab | Troj.W32.Buzus |
| Agnitum | Packed/PECompact |
| Antiy-AVL | Trojan/Win32.Genome, VCS/PEStruct.RsrcPatchedPE, Trojan/Win32.Agent.gen, Trojan/Win32.Tgenic |
| Baidu | HEUR.Win32.Virus.Lamer.g |
| CAT-QuickHeal | (Suspicious) - DNAScan |
| CMC | Heur.Win32.Obfuscated.1!O, Trojan.Win32.Agentmpact!O |
| ClamAV | Win.Trojan.Katusha-477, Win.Trojan.Bancos-2115 |
| Comodo | TrojWare.Win32.Agent.KFHU |
| DrWeb | Trojan.DownLoader5.44566, DLOADER.Trojan |
| Emsisoft | Win32.Expiro.BE (B), Win32.Expiro.BK (B), Adware.BetterSurf.F (B), Gen:Variant.Zusy.52984 (B), Trojan.Generic.6317698 (B), Gen:Adware.MPlug.1 (B) |
| Ikarus | PUA.InstallIQ |
| Jiangmin | Trojan/Banker.Agent.bgj |
| K7AntiVirus | Spyware |
| Rising | PE:Malware.XPACK/RDM!5.1, PE:Malware.XPACK-HIE/Heur!1.9C48 |
| TheHacker | Posible_Worm32 |
| TrendMicro-HouseCall | TROJ_GEN.F47V0716, TROJ_GEN.F47V0914, TROJ_GEN.F47V1010 |
| Zillya | Adware.DealKeeper.Win32.2270 |
| eSafe | Suspicious File |
| eTrust-Vet | Win32/Sality.AA |
* How the Detection Percentage is Calculated
The detection percentage is based on the fact that I've collected 52253 scan results for the Symantec Corporation files. 41 of these scan results came up with some sort of detection. If you like, you can review the full details of the scan results by examining the files listed above.
Analysis Details
The analysis is based on certificates with the following serial numbers:
- 758f5ee8263b6694719d8434eb998608
- 66660552d465b31f429f7527ea6a93bf
- 5c61f2c32ffb8a0baead0f61cf07abde
- 7f4ba50bf9970fcca0b242179e964657
- 01edf8340cdf060c099e1a6472f76db4
- 2bbaf83d7bedd958309d62b93ee41074
- 12db9e53539b8e248bc77dd2ba611167
- 4a9171b8cafa5e2b2a1370e12d8b0d58
- 0ebfea68d677b3e26cab41c33f3e69de
- 07aefa759e91a33a48378b09de488822
- 4bda438e6927c946a49add3e6ac9dad2
- 035f9a870e1dcb22429e23c72621c313