WZT - 14% Detection Rate *

Did you just stumble upon a download or a file on your computer that has a digital signature from WZT? Some of the security products refers to the detected files as Trojan.Win32.Generic!BT and HackTool.AutoKMS. The detection rate for the WZT files collected here is 14%. Please read on for more details.

You will probably see WZT when double-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 WZT appears as the verified publisher in the UAC dialog

You can view the additional details from the WZT digital signature with the following steps:

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

Here is a screengrab of a file signed by WZT:

Screenshot of the WZT certificate

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 WZT and that the file has not been tampered with.

If you click the View Certificate button shown in the screenshot above, you can see 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 view the address for WZT, such as the street name, city and country.

WZT has issued the WZT certificates. You can also see the details of the issuer by clicking the View Certificate button shown in the screencap above.

WZT Files

These are the WZT files I have gathered, thanks to the FreeFixer users.

Detection RatioFile Name
23/57AAct.exe
7/55KMSCleaner.exe
24/56KMSSS.exe
5/54TunMirror2.exe

Scanner and Detection Names

Here's the detection names for the WZT files. I have grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.

ScannerDetection Names
AVGPatched5_c.FMV, HackTool.ASVR, Patched4_c.BDR
AVwareTrojan.Win32.Generic!BT
AegisLabSpr.Hackkms.Sgde!c, Troj.Generickd!c
AhnLab-V3HackTool/Win32.Activator.C1521067, Unwanted/Win32.HackTool.R170046
AviraSPR/HackKms.sgde.6
BaiduHEUR.Win32.Virus.Lamer.g
Baidu-InternationalHacktool.Win32.HackKMS.W
BkavW32.Clodd07.Trojan.ece3
CyrenW32/Trojan.BZQC-5565, W32/Trojan.WPVF-4427, W32/Trojan.ECSM-5012
ESET-NOD32a variant of Win64/HackKMS.I potentially unsafe, a variant of Win32/HackTool.KMSAuto.E potentially unsafe, a variant of Win32/HackKMS.W potentially unsafe, a variant of MSIL/HackTool.TunMirror.A potentially unsafe
FortinetRiskware/HackKMS
GDataWin32.Application.Agent.FIGC8G
IkarusHackTool.AutoKMS
JiangminTrojan.GenericKD.adt, Worm.Mamianune.ej
K7AntiVirusUnwanted-Program ( 004d8d201 ), Unwanted-Program ( 004cf8181 )
K7GWUnwanted-Program ( 004d8d201 ), Unwanted-Program ( 004cf8181 )
MalwarebytesHackTool.AutoKMS
McAfeeRDN/Generic PUP.x, RDN/Generic PUP.z, Artemis!3B33E3AB6E91
McAfee-GW-EditionRDN/Generic PUP.x, RDN/Generic PUP.z, Artemis
MicrosoftHackTool:Win32/AutoKMS
PandaTrj/CI.A
SUPERAntiSpywareHack.Tool/Gen-HackKMS
SophosGeneric PUA IM (PUA), Generic PUA BH (PUA)
SymantecML.Relationship.HighConfidence [Trojan.Gen.2], Suspicious.Cloud, Trojan.Gen.2
TencentWin32.Trojan.Ramnit.Dzkk
TrendMicroTROJ_GEN.R08JC0OIK16, TROJ_GEN.R00XC0EKH15
TrendMicro-HouseCallTROJ_GEN.R08JC0OIK16
VIPRETrojan.Win32.Generic!BT
YandexPUP.Agent!
ZillyaAdware.BrowseFox.Win32.145930
nProtectTrojan/W32.Agent.713328

* How the Detection Percentage is Calculated

The detection percentage is based on the fact that I have gathered 416 scan results for the WZT files. 59 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 done on certificates with the following serial numbers:

Comments

No comments posted yet.

Leave a reply