Microsoft Windows Hardware Compatibility Publisher - 0.076% Detection Rate *

Did you just find a download or a file on your computer that has been digitally signed by Microsoft Windows Hardware Compatibility Publisher? If that's the case, please read on.

You'll typically notice Microsoft Windows Hardware Compatibility Publisher when clicking to run the file. The publisher name is then displayed as the "Verified publisher" in the UAC dialog as the screenshot shows:

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

You can view additional details from the Microsoft Windows Hardware Compatibility Publisher certificate with the following procedure:

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

Here is a screenshot of a file signed by Microsoft Windows Hardware Compatibility Publisher:

Screenshot of the Microsoft Windows Hardware Compatibility Publisher certificate

As you can see in the screenshot above, Windows states that "This digital signature is OK". This means that the file has been published by Microsoft Windows Hardware Compatibility Publisher and that the file has not been tampered with.

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 Microsoft Windows Hardware Compatibility Publisher, such as the street name, city and country.

Microsoft Windows Hardware Compatibility PCA, Microsoft Windows Hardware Compatibility, Microsoft Windows Third Party Component CA 2012 and Microsoft Windows Third Party Component CA 2014 has issued the Microsoft Windows Hardware Compatibility Publisher certificates. You can also see the details of the issuer by clicking the View Certificate button shown in the screengrab above.

Microsoft Windows Hardware Compatibility Publisher Files

The following are the Microsoft Windows Hardware Compatibility Publisher files I have gathered, thanks to the FreeFixer users.

The FreeFixer tool treats files from Microsoft Windows Hardware Compatibility Publisher as safe, which means that the Microsoft Windows Hardware Compatibility Publisher 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 Microsoft Windows Hardware Compatibility Publisher file(s). I'm pretty sure those detections are false positives and that the files are safe. It's unlikely that Microsoft Windows Hardware Compatibility Publisher would ship a malware file.

Detection RatioFile Name
2/50smax4pnp.exe
1/53igfxpers.exe
1/47SkyTel.EXE
1/48Ati2mdxx.exe
2/51hasplms.exe
1/49fasttx2k.sys
1/53PAStiSvc.exe
1/53Ati2evxx.exe
1/66TwDsUiLaunch.exe
1/52igfxpers.exe
2/50aksfridge.sys
1/51igfxpers.exe
1/48hkcmd.exe
2/49igfxpers.exe
1/49igfxtray.exe
1/50igfxpers.exe
1/47Ati2evxx.exe
1/49vsnpstd.exe
1/51nvsvc32.exe
1/49viprt.sys
1/55Ati2evxx.exe
1/48atiesrxx.exe
1/48Ati2evxx.exe
1/52igfxpers.exe
1/48hasplms.exe
1/55Ati2evxx.exe
1/52stacsv.exe
1/52vsnp2std.exe
1/48hardlock.sys
1/51nvsvc32.exe
1/51hkcmd.exe
1/51atiesrxx.exe
1/50Ati2evxx.dll
1/47SOUNDMAN.EXE
1/46stacsv64.exe
1/47aksfridge.sys
2/55sm56hlpr.exe
1/51hpowiav1.dll
1/47ps2.exe
1/47nv_agp.sys
1/48NvMcTray.dll
1/51ApntEx.exe
1/52hkcmd.exe
1/51zstatus.exe
1/47iastor.sys
1/51hkcmd.exe
1/51vsnpstd.exe
1/54viamraid.sys
2/46CAP3RSK.EXE
1/42sm56hlpr.exe
1/46E_DMSG00.EXE
1/55fspuip.exe
1/50sm56hlpr.exe
1/51atiesrxx.exe
1/48atieclxx.exe
1/68TwDsUiLaunch.exe
1/54igfxpers.exe
1/66atieclxx.exe
1/40igfxrTRK.lrc
1/48aksfridge.sys
2/54igfxsrvc.exe
1/48BrmfBAgS.exe
1/49SynTPEnh.exe
2/56hasplms.exe
1/46aksdf.sys
1/50E_FUICLBE.DLL
1/42essspk.exe
1/50SynTPEnh.exe
1/51sm56hlpr.exe
2/55hasplms.exe
1/45hardlock.sys
1/52atiesrxx.exe
1/55VIASysFx.dll
1/55DptfPolicyLpmServiceHelper.exe
1/50CTHELPER.EXE
1/45SOUNDMAN.EXE
1/42E_FATIABE.EXE
1/49igfxtray.exe
1/56sttray.exe
1/52atiesrxx.exe
1/43CAP3LAK.EXE
1/50igfxpers.exe
1/48aksfridge.sys
1/46hardlock.sys
1/48SynToshiba.exe
1/41stapo.dll
1/51escndv.exe
1/53vspc1000.exe
3/46jraid.sys
1/57adgnetworktdidrv.sys
1/68TwDsUiLaunch.exe
1/45hardlock.sys
2/49STacSV.exe
4/47S3trayp.exe
2/50ahcix86.sys
1/40hposwia_p01d.dll
1/50E_IUICFCE.DLL
1/54esxw2ud.dll
2/64adgnetworktdidrv.sys
1/66TmUmEvt.dll
1/50atiesrxx.exe
1/42E_FATIAEL.EXE
1/51nvraid.sys
1/50stacsv.exe
1/43LEXBCES.EXE
1/49sm56hlpr.exe
1/33Ati2evxx.exe
1/46CNMUI83.DLL
1/49netaapl.sys
1/48anodlwf.sys
1/51atiesrxx.exe
1/54SynTPAPI.dll
1/54atiesrxx.exe
1/55hccutils.DLL
1/54nvsvc32.exe
1/53atieclxx.exe
1/49CNC_AQL.dll
1/55fpapli.exe
1/56ati2evxx.exe
1/51ubsbm.sys
1/50sbavmon.dll
1/54Ati2evxx.exe
1/54hkcmd.exe
1/52aticfx32.dll
1/57aksdf.sys
1/54atiesrxx.exe
1/56igfxtray.exe
1/58OSD.exe
1/58UIUCU.EXE
1/65VM331_STI.EXE
1/67StlFspAPI32.dll
1/67TwDsUiLaunch.exe
1/67TwDsUiLaunch.exe
1/69TwDsUiLaunch.exe
0/52igfxdev.dll
0/48igfxsrvc.dll
0/50mdmxsdk.sys
0/52igfxdev.dll
0/52ALCMTR.EXE
0/51igfxsrvc.dll
0/52igfxdev.dll
0/51mdmxsdk.sys
0/50tiltwheel%USERNAME%.exe
0/48ALCXMNTR.EXE

Scanner and Detection Names

Here's the detection names for the Microsoft Windows Hardware Compatibility 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 false positives since it is very unlikely that Microsoft Windows Hardware Compatibility Publisher would ship a malware file.

ScannerDetection Names
AegisLabTroj.W32.Gen.m2M2, AdWare.W32.BrainInst, W32.Virut
AgnitumTrojan.Inject!lsJh8B2mO2g
Antiy-AVLTrojan/Win32.Tgenic, Trojan/Win32.Menti, Worm/Win32.Otwycal, Trojan/Win32.SGeneric, Trojan[:HEUR]/Win32.Unknown, Worm/Win32.Otwycal.gen, Worm/Win32.Klez.gen, Worm/Win32.WhiteIce.gen, Backdoor/Win32.Bifrose.gen, Trojan/Win32.Agent
AviraWORM/Conficker.Z.32
BaiduWin32.Trojan.WisdomEyes.16070401.9500.9504, Win32.Trojan.WisdomEyes.16070401.9500.9669
Baidu-InternationalHacktool.Win64.NetFilter.A
BkavHW32.CDB.9be0, HW32.CDB.8117, W32.Clodaed.Trojan.4969, W32.HfsAutoA.Ffc1, HW32.CDB.619b, W32.Clodbae.Trojan.b5af, HW32.CDB.3205, HW32.Laneul.jsmg, W32.Clodea0.Trojan.d774, HW32.CDB.Bbe4, HW32.Laneul.hykq, W32.HfsAutoA.B76C, HW32.Packed.ECC9, HW32.CDB.F961, HW32.Laneul.juio, W32.Clod861.Trojan.2fb2, HW64.packed.9E7E, HW32.Nonim.wqsy, HW32.Nonim.xuak, W32.HfsReno.8a5c, HW64.packed.A908
ByteHeroTrojan.Exception.gen.101, Trojan-Dropper.win32.Agent.a
CMCHeur.Win32.Obfuscated.1!O
ClamAVWin.Trojan.7507983, Win.Trojan.Agent-564482, Win.Trojan.Rootkit-6573, Win.Trojan.6536826, Win.Trojan.Agent-343335, Win.Trojan.Agent-230945, PUA.Win32.Packer.Msvcpp-1, Win.Trojan.Agent-576433, Win.Trojan.Slugin-357
ComodoUnclassifiedMalware
CylanceUnsafe
DrWebBackDoor.Siggen.41201, DLOADER.Trojan
EmsisoftGen:Trojan.Heur.LP.ay4@aCPH@bli (B), Trojan.Generic.KDV.530539 (B), Win32.Worm.AutoIt.Z (B), Android.Adware.Kuguo.A (B), JS:Trojan.Clicker.NBP (B), Gen:Variant.Graftor.127006 (B), Android.Trojan.FakeInst.DA (B)
Invinceavirus.win32.sality.at
JiangminTrojan/Reconyc.fid, Win32/Virut.bn, I-Worm/Polip.cl, Trojan.Cosmu.i
KingsoftWin32.Troj.Agent2.cq.(kcloud)
McAfee-GW-EditionHeuristic.BehavesLike.Win32.Suspicious-DTR.K, Heuristic.LooksLike.Win32.Suspicious.I, Heuristic.LooksLike.Win32.Suspicious.B, Heuristic.LooksLike.Win32.Suspicious.E, BehavesLike.Win32.PWSZbot.dh
NANO-AntivirusTrojan.Win32.Cholera.ctdfbm, Trojan.Win32.Inject.cslkna, Trojan.Win32.Agent.derwez, Trojan.Win32.Warezov.daszf, Trojan.Win32.Graftor.cticpm, Trojan.Win32.IframeExec.cxhgiu, Trojan.Win32.Heuristic210.dfvtzs
PrevxMedium Risk Malware
RisingPE:Trojan.Barys!6.50A, PE:Malware.XPACK-HIE/Heur!1.9C48, PE:Adware.OneStep!6.161D, PE:Trojan.Symmi!6.804, PE:Malware.Viking!6.17A9, PE:Backdoor.Agent!6.13D4, PE:Worm.Chir!6.171E, PE:Rootkit.Agent!6.2332
SymantecSuspicious.Insight
TheHackerBackdoor/IRCNite.arz, Trojan/VB.qdc, Trojan/Menti.mxvf, Trojan/Agent.sjtk, Trojan/VBKrypt.efmc, Backdoor/IRCNite.cei, Trojan/Menti.myha, Trojan/AutoRun.AntiAV.t, Backdoor/Bredavi.eks, Trojan/Small.nav
Trapminemalicious.moderate.ml.score
TrendMicro-HouseCallTROJ_GEN.R0CBH0AA314, TROJ_GEN.F47V0201, Suspicious_GEN.F47V0818
VBA32Trojan.Menti, Trojan.Agent, Trojan.Agent.ashi, Virus.Win32.Virut.X6
ViRobotTrojan.Win32.A.ShipUp.1404928, Trojan.Win32.A.NSAnti.102400.X, Trojan.Win32.A.Menti.90112.EH
Webwasher-GatewayBlockReason.0
YandexRiskware.Agent!
ZillyaTrojan.Monder.Win32.49829, Trojan.Menti.Win32.35788
eGambitUnsafe.AI_Score_91%
eSafeWin32.TrojanHorse, Win32.Trojan
nProtectTrojan/W32.Agent.405504.XW, Trojan/W32.Agent.544768.L, Trojan-Downloader/W32.Cekar.61512

* How the Detection Percentage is Calculated

The detection percentage is based on that I have gathered 197480 scan reports for the Microsoft Windows Hardware Compatibility Publisher files. 151 of these scan results came up with some sort of detection. You can review the full details of the scan results by examining the files listed above.

Analysis Details

The analysis has been done on certificates with the following serial numbers:

Comments

No comments posted yet.

Leave a reply