kprocesshacker.sys threat report

MD5 e3b9f60e3b26e765d884cc99344ae7cb
Latest seen 2021-01-10 16:33:18 (5 years ago)
First seen 2021-01-10 16:33:18 (5 years ago)
Size 56 KB
Publisher wj32
Product KProcessHacker

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Risk.ProcessHacker. 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
Risk.ProcessHacker
Recommended action
Scan and remove
Last analysis
2021-01-10 16:33:18 (5 years ago)
File hash
e3b9f60e3b26e765d884cc99344ae7cb
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Risk.ProcessHacker.

Timeline

First seen 2021-01-10 16:33:18 (5 years ago); latest analysis 2021-01-10 16:33:18 (5 years ago).

Publisher context

Company metadata: wj32. Product metadata: KProcessHacker.

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.

kprocesshacker.sys is a Windows file recorded in the ThreatInfo database. It is associated with KProcessHacker. The reported company name is wj32. The current detection status is Risk.ProcessHacker, based on the latest analysis from 2021-01-10 16:33:18 (5 years ago).

If kprocesshacker.sys 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 Risk.ProcessHacker.

Product Name: KProcessHacker
Company Name: wj32
MD5: e3b9f60e3b26e765d884cc99344ae7cb
Size: 56 KB
First Published: 2021-01-10 16:33:18 (5 years ago)
Latest Published: 2021-01-10 16:33:18 (5 years ago)
Status: Risk.ProcessHacker (on last analysis)
Analysis Date: 2021-01-10 16:33:18 (5 years ago)
kprocesshacker.sys 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.

%programfiles%

ThreatInfo has observed kprocesshacker.sys 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.

100.0%

The strongest geographic signal for this file is Poland with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

The most common operating system signal for kprocesshacker.sys is Windows 10 with 100.0% 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.

kprocesshacker.sys is identified as pe for 32 systems. The subsystem is Native. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Native
PE Type: pe
OS Bitness: 32
Image Base: 0x00010000
Entry Address: 0x0000f005

PE Sections:

Name Size of data MD5
.text 16384 aaa1a1bf35dc616897a5fe9ba97ca259
.rdata 4608 833bfd72d81a7a7dfeabe1fcc622f92b
.data 12288 6e307772bbb5be4ad239449650469bf7
PAGE 15360 ef1430128480704053290c24a44d78e3
INIT 3584 8929ee51e733f3b76451abbc87e2f3ee
.rsrc 1024 03a8a3fcd557fde5cd240583e63cf337
.reloc 3584 0f0fb9d362c7ef1c06cb89bb43300dde

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.

More information: