GridinSoft Threat Intelligence

00000051 threat report

Detected as Hack.KMS File reputation report
MD5 b85f4ce841f3ae1ebdf76835d2eadbef
Latest seen 2026-05-27 17:00:37 (18 hours ago)
First seen 2017-05-24 20:03:02 (9 years ago)
Size 13 KB
Signed by WZT

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Hack.KMS. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Hack.KMS
Recommended action
Scan and remove
Last analysis
2026-05-27 17:00:37 (18 hours ago)
File hash
b85f4ce841f3ae1ebdf76835d2eadbef
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Hack.KMS, part of the Hack threat category.

Category context

Tools used to bypass protections, alter software behavior, or enable unauthorized access. Related Hack reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2017-05-24 20:03:02 (9 years ago); latest analysis 2026-05-27 17:00:37 (18 hours ago).

Digital signature

Signed by WZT. The signature is not reported as trusted and valid, which can indicate tampering, repackaging, or copied publisher data.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present. Review the Hack category for related samples and common context.

00000051 is a Windows file recorded in the ThreatInfo database. The current detection status is Hack.KMS, based on the latest analysis from 2026-05-27 17:00:37 (18 hours ago). ThreatInfo groups this verdict with Hack reports for broader family-level investigation.

If 00000051 appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Hack.KMS.

MD5: b85f4ce841f3ae1ebdf76835d2eadbef
Size: 13 KB
First Published: 2017-05-24 20:03:02 (9 years ago)
Latest Published: 2026-05-27 17:00:37 (18 hours ago)
Status: Hack.KMS (on last analysis)
Analysis Date: 2026-05-27 17:00:37 (18 hours ago)
00000051 detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

Signed By: WZT
Status: Invalid (digital signature could be stolen or file could be patched)

The signature on 00000051 is not reported as trusted and valid. Invalid or suspicious signature data can indicate tampering, repackaging, or an unrelated file using copied publisher information.

%commonappdata%\kmsautos\bin\driver\x64wdv
%commonappdata%\kmsauto\bin\driver\x64wdv
%sysdrive%\windows.old\programdata\kmsautos\bin\driver\x64wdv
%appdata%\zhp\quarantine\kmsautos\bin\driver\x64wdv
%sysdrive%\$recycle.bin\s-1-5-21-2275429643-1357250638-3055656149-1001\$rjaj0uu\bin\driver\x64wdv
%commonappdata%\kmsautos\bin\driver
%commonappdata%\kmsauto\bin\driver
%appdata%\zhp\quarantine\kmsauto\bin\driver
%sysdrive%\$recycle.bin
%appdata%\zhp\quarantine\kmsautos\bin\driver

ThreatInfo has observed 00000051 in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

FakeClient.exe $R5EXLYY.exe $RB3CBLV.exe FakeClient(152).exe 00000051

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Windows 10 82.6%
Windows 7 10.0%
Windows 8.1 6.1%
Windows 8 0.5%
Windows Server 2012 R2 0.3%
Windows Server 2008 R2 0.2%
Windows Embedded 8.1 0.1%
Windows Server 2016 0.1%

The most common operating system signal for 00000051 is Windows 10 with 82.6% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

00000051 is identified as pe for 64-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 64-bit
Subsystem Windows CUI
Entry point 0x000012fc
Image base 0x0000000140000000

PE Sections:

Sections 6
Raw data 8704

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 3584 bytes · 41.2% of section data
MD5 f8517e2e06a0264d414dac4fcb846c29
.rdata 3072 bytes · 35.3% of section data
MD5 adb76d07d82659b2e10b2b3acc3db7b7
.data 512 bytes · 5.9% of section data
MD5 04d489f71119c8a139d74098d1680891
.pdata 512 bytes · 5.9% of section data
MD5 516aab97049c71124ac40d5b54cdc95c
.rsrc 512 bytes · 5.9% of section data
MD5 df9214180541147e51ae67c9a5ca59ac
.reloc 512 bytes · 5.9% of section data
MD5 aec081bf54f5bd13a0a802758e7496ea

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

Report conclusion

GridinSoft detects this file as Hack.KMS

This report identifies 00000051 by MD5 b85f4ce841f3ae1ebdf76835d2eadbef. It is part of the Hack report group. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.

Download GridinSoft Anti-Malware Scan the device and confirm whether this exact hash is present. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with b85f4ce841f3ae1ebdf76835d2eadbef.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan and remove the object if the same hash is found. Use the Hack category to compare similar reports.