GridinSoft Threat Intelligence

DotNetTools.dll file report

Under review File reputation report
MD5 15ab3740703138ed5c091ea7736620f4
Latest seen 2025-11-26 23:01:14 (6 months ago)
First seen 2018-11-03 13:12:45 (7 years ago)
Size 111 KB
Publisher wj32
Product .NET tools plugin for Process Hacker
Signed by Wen Jia Liu

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-11-03 13:12:45 (7 years ago); latest analysis 2025-11-26 23:01:14 (6 months ago).

Publisher context

Company metadata: wj32. Product metadata: .NET tools plugin for Process Hacker.

Digital signature

Signed by Wen Jia Liu. The signature is reported as valid, but signed files can still be bundled or abused.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

File context

DotNetTools.dll is a Windows file recorded in the ThreatInfo database. It is associated with .NET tools plugin for Process Hacker. The reported company name is wj32. The current detection status is Undefined, based on the latest analysis from 2025-11-26 23:01:14 (6 months ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

File Details

Product Name: .NET tools plugin for Process Hacker
Company Name: wj32
MD5: 15ab3740703138ed5c091ea7736620f4
Size: 111 KB
First Published: 2018-11-03 13:12:45 (7 years ago)
Latest Published: 2025-11-26 23:01:14 (6 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-11-26 23:01:14 (6 months ago)

Overview

Signed By: Wen Jia Liu
Status: Valid

The signature on DotNetTools.dll 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:

%appdata%
%programfiles%\process hacker 2\x86
%programfiles%\process hacker 2
%sysdrive%\cracking files & tweets\process hacker\x86
%sysdrive%\tech & tools files\process hacker\x86
%sysdrive%\cracking files & tweets\cracking files & tweets\process hacker\x86
%sysdrive%\process hacker 2\x86
%sysdrive%\work station\service\processhacker-2.39-bin\x86
%desktop%\jwk\img\wa\process hacker 2\x86
%sysdrive%\filehistory\jhk\main\data\c\users\jhk\desktop\jwk\img\wa\process hacker 2\x86

ThreatInfo has observed DotNetTools.dll 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.

Geographic signal

Observed country distribution

ThreatInfo has seen DotNetTools.dll across 26 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 12.9%
Low High activity

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

OS Version:

Windows 10 77.8%
Windows 7 17.5%
Windows Server 2008 R2 1.6%
Windows 8.1 1.6%
Windows Server 2012 R2 1.6%

The most common operating system signal for DotNetTools.dll is Windows 10 with 77.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

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

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x0000695f
Image base 0x10000000

PE Sections:

Sections 6
Raw data 105472

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

.text 61440 bytes · 58.3% of section data
MD5 ae1ecb5643bfb7516f659aeed165b8a5
.rdata 33280 bytes · 31.6% of section data
MD5 6a155af9f5c88ff7b2d69d8a8d02e358
.data 2560 bytes · 2.4% of section data
MD5 f854147579a38e4477f0aee8bbda19ea
.gfids 512 bytes · 0.5% of section data
Uncommon name
MD5 e30bcd7f5212884e68f9859f582d8c99
.rsrc 2560 bytes · 2.4% of section data
MD5 4ed2f745221093b04c1d7f4215841bc7
.reloc 5120 bytes · 4.9% of section data
MD5 4cc963ac9a101ac7ddae51e57cc7d55a

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

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 15ab3740703138ed5c091ea7736620f4.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.