kprocesshacker.sys threat report
ThreatInfo file report
kprocesshacker.sys
This report summarizes the file identity, detection status, publisher metadata, observed locations, and technical indicators for kprocesshacker.sys. ThreatInfo currently classifies this sample as Hack.Patcher.
GridinSoft Anti-Malware detection
GridinSoft already detects this file
The latest ThreatInfo record shows kprocesshacker.sys detected as Hack.Patcher. You can download GridinSoft Anti-Malware to scan the system and remove this detection if the file is present on your device.
- Detection name
- Hack.Patcher
- Last analysis
- 2022-05-08 23:30:30 (3 years ago)
- File hash
- 76be68ce3484169b8e5709a36bb622ba
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 Hack.Patcher, based on the latest analysis from 2022-05-08 23:30:30 (3 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 Hack.Patcher.
File Details
| Product Name: | KProcessHacker |
| Company Name: | wj32 |
| MD5: | 76be68ce3484169b8e5709a36bb622ba |
| Size: | 40 KB |
| First Published: | 2019-08-11 00:37:24 (6 years ago) |
| Latest Published: | 2022-05-08 23:30:30 (3 years ago) |
| Status: | Hack.Patcher (on last analysis) | |
| Analysis Date: | 2022-05-08 23:30:30 (3 years ago) |
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.
Overview
| Signed By: | Wen Jia Liu |
| Status: | Valid |
The signature on kprocesshacker.sys is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.
Common Places:
| %desktop%\10_anti\data\ph |
| %sysdrive%\system volume information\_restore{79c0aeb3-efaf-4165-8058-6605d77921e8} |
| %sysdrive%\system volume information\_restore{79c0aeb3-efaf-4165-8058-6605d77921e8} |
| %sysdrive%\system volume information\_restore{79c0aeb3-efaf-4165-8058-6605d77921e8} |
| %desktop%\injector |
| %sysdrive%\portable\proces_s_h_a_c_k_e_r_3.0.2471_nb_portable.7z\process_hacker_3.0.2471_nb_portable\app\processhacker |
| %sysdrive%\process_hacker_v3.0_rus\process_hacker_v3.0_rus |
| %desktop%\1qqqq\1\choose any injector\process hacker v3 |
| %profile%\downloads\processhacker-build-bin |
| %profile%\downloads\processhacker-build-bin |
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.
Geography:
| 50.0% | ||
| 10.4% | ||
| 6.3% | ||
| 6.3% | ||
| 6.3% | ||
| 4.2% | ||
| 4.2% | ||
| 4.2% | ||
| 4.2% | ||
| 2.1% | ||
| 2.1% |
The strongest geographic signal for this file is Turkey with 50.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
| Windows 8.1 | 47.8% | |
| Windows 10 | 43.5% | |
| Windows 7 | 8.7% |
The most common operating system signal for kprocesshacker.sys is Windows 8.1 with 47.8% 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.
Analysis
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: | 0x0000703e |
PE Sections:
| Name | Size of data | MD5 |
| .text | 3072 | 9296841dd9f2689716e1b70ed4e6d00e |
| .rdata | 2048 | 23ed1666797185a927439cca12d70dce |
| .data | 512 | 9eec23851ccd108f57b2c18b37be628e |
| PAGE | 12288 | 6f84618972e6fc68b9234ce15d069c7c |
| INIT | 2560 | 6d4bf5f911f0c4a0fd137e70bd0c9057 |
| .rsrc | 1024 | a553841eeb097d0c22d509edcc6ccefb |
| .reloc | 1536 | 62c95332abd9980cae4de75e973fb497 |
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:
