Microsoft Windows Component Publisher - 0.049% Detection Rate *

Did you just download a file that is digitally signed by Microsoft Windows Component Publisher and wonder if the file is safe? If that's the case, please read on.

You will probably see Microsoft Windows Component Publisher when clicking to run the file. The publisher name shows up as the "Verified publisher" in the UAC dialog as the screenshot shows:

Screenshot where Microsoft Windows Component Publisher appears as the verified publisher in the UAC dialog

You can view the digital signature details for Microsoft Windows Component Publisher with the following procedure:

  1. Open up Windows Explorer and locate the Microsoft Windows Component Publisher file
  2. Right-click on the file and select Properties
  3. Click the Digital Signatures tab
  4. Click on the View Certificate button

Here's a screencap of a file digitally signed by Microsoft Windows Component Publisher:

Screenshot of the Microsoft Windows Component Publisher certificate

As you can see in the screenshot above, the Windows OS states that "This digital signature is OK". This implies that the file has been published by Microsoft Windows Component Publisher and that no one has tampered with the file.

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 see the address for Microsoft Windows Component Publisher, such as the street name, city and country.

Microsoft Windows Verification Intermediate PCA and Microsoft Windows Verification PCA has issued the Microsoft Windows Component Publisher certificates. You can also view the details of the issuer by clicking the View Certificate button shown in the screenshot above.

Microsoft Windows Component Publisher Files

These are the Microsoft Windows Component Publisher files I've collected, thanks to the FreeFixer users.

The FreeFixer tool treats files from Microsoft Windows Component Publisher as safe, which means that the Microsoft Windows Component Publisher 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 Microsoft Windows Component Publisher file(s). My guess is that those detections are incorrect and that the files are safe. It is unlikely that Microsoft Windows Component Publisher would ship a malware file.

Detection RatioFile Name
1/500
1/41msratelc.dll
1/500
1/50rstrui.exe
2/51Explorer.EXE
1/50MSVBVM60.DLL
1/51ctfmon.exe
1/51ctfmon.exe
1/48jsproxy.dll
1/50iertutil.dll
1/55svchost.exe
1/54userinit.exe
1/57svchost.exe
1/50AhnRpta.exe
1/47AcGenral.DLL
1/43setupSNK.exe
1/48catsrvut.dll
1/46msctfime.ime
1/48MSVBVM60.DLL
1/36ddraw.dll
1/47xpshims.dll
2/55rundll32.exe
1/54tcpip.sys
1/54windowscodecs.dll
1/68RPCRT4.dll
1/69autochk.exe
1/68setup.exe
0/52WPDShServiceObj.dll
0/51msacm32.drv
0/52wdfmgr.exe
0/51xpnetdiag.exe
0/52filterpipelineprintproc.dll
0/53autochk.exe
0/52wdfmgr.exe
0/52secdrv.sys
0/52044240b77972b156cddab103aae0e21f
0/51wlnotify.dll

Scanner and Detection Names

Here is the detection names for the Microsoft Windows Component Publisher 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 Microsoft Windows Component Publisher would ship a malware file.

ScannerDetection Names
APEXMalicious
AegisLabW32.Virut, DangerousObject.Multi.Gen
BaiduWin32.Trojan.WisdomEyes.16070401.9500.9773
BkavHW32.Inectrj.kwwg
ByteHeroTrojan-Downloader.Win32.Tiny.cmq
ClamAVTrojan.Patched-372, Win.Trojan.Bancos-2115
ComodoHeur.Suspicious
EmsisoftGen:Variant.Kazy.327376 (B), Android.Adware.Wallap.A (B), Gen:Variant.Strictor.47446 (B)
JiangminTrojan/Agent.jjlp
MalwarebytesMalware.Heuristic.1001
McAfee-GW-EditionHeuristic.BehavesLike.Win32.Suspicious-BAY.K
RisingPE:Trojan.VBKeyLogger!1.9F6C
SUPERAntiSpywareTrojan.Agent/Gen-Dynamer
TheHackerTrojan/Generic.nodef, Trojan/Downloader.Geral.ngf, Trojan/Fesber.a, Trojan/PSW.LdPinch.andx
VBA32Trojan-GameThief.Win32.OnLineGames.bnib
ViRobotTrojan.Win32.A.NSAnti.33280.R
eSafeWin32.Banker
nProtectTrojan/W32.BHO.25600.D, Trojan/W32.Agent.69632.PY

* How the Detection Percentage is Calculated

The detection percentage is based on the fact that I have collected 58895 scan reports for the Microsoft Windows Component Publisher files. 29 of these scan results came up with some sort of detection. You can view 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:

Comments

Donna Poole writes

1 thumb

need to detect errors

# 9 Sep 2016, 10:12

Leave a reply