ToolStatus.dll file report

MD5 837ef2b8f202ab9f53545fa2bc7fe71e
Latest seen 2025-11-26 23:01:13 (6 months ago)
First seen 2019-07-28 08:42:18 (6 years ago)
Size 223 KB
Publisher dmex
Signed by Wen Jia Liu

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-07-28 08:42:18 (6 years ago); latest analysis 2025-11-26 23:01:13 (6 months ago).

Publisher context

Company metadata: dmex. Product metadata: ToolStatus 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.

ToolStatus.dll is a Windows file recorded in the ThreatInfo database. It is associated with ToolStatus plugin for Process Hacker. The reported company name is dmex. The current detection status is Undefined, based on the latest analysis from 2025-11-26 23:01:13 (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.

Product Name: ToolStatus plugin for Process Hacker
Company Name: dmex
MD5: 837ef2b8f202ab9f53545fa2bc7fe71e
Size: 223 KB
First Published: 2019-07-28 08:42:18 (6 years ago)
Latest Published: 2025-11-26 23:01:13 (6 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-11-26 23:01:13 (6 months ago)
Signed By: Wen Jia Liu
Status: Valid

The signature on ToolStatus.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.

%programfiles%\process hacker 2
%sysdrive%\cracking files & tweets\cracking files & tweets\process hacker\x86
%sysdrive%\cracking files & tweets\process hacker\x86
%sysdrive%\tech & tools files\process hacker\x86
%sysdrive%\work station\service\processhacker-2.39-bin\x86
%desktop%\todo\windows10\process hacker 2
%sysdrive%\drivers & programms\antivirus\processhacker-2.39\x86
%profile%\downloads\processhacker-2.39-bin\x86
%programfiles%\process hacker 2
%profile%\downloads\processhacker-2.39-bin\x86

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

18.8%
18.8%
12.5%
6.3%
6.3%
6.3%
6.3%
6.3%
6.3%
6.3%
6.3%

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

Windows 10 75.0%
Windows 7 25.0%

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

ToolStatus.dll is identified as pe for 32 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x10000000
Entry Address: 0x00009aa3

PE Sections:

Name Size of data MD5
.text 73216 32d3fd53c7e22eb55543ff735a5086cf
.rdata 33280 6a9920f767473b7df2f258aa5f290325
.data 2560 d95fce6513a9927f8b523aa7d299906c
.gfids 512 beb5da8223fcaa290f33624d4694a375
.rsrc 103936 3b1839d7c01fa52f4ce6d6d8977e8733
.reloc 7168 0b0b2894e9275c17e36535ca5ffc335e

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: