GridinSoft Threat Intelligence

ToolStatus.dll file report

Under review File reputation report
MD5 3788efff135f8b17a179d02334d505e6
Latest seen 2025-11-26 23:01:13 (6 months ago)
First seen 2019-06-15 17:43:33 (6 years ago)
Size 243 KB
Publisher dmex
Signed by Wen Jia Liu

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Category context

Programs that inject advertising, change browser behavior, or monetize traffic through bundled components. Related Adware reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2019-06-15 17:43:33 (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 groups this verdict with Adware reports for broader family-level investigation.

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: 3788efff135f8b17a179d02334d505e6
Size: 243 KB
First Published: 2019-06-15 17:43:33 (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.

%commonappdata%\msconfig\apps\x64
%programfiles%\process hacker 2
%sysdrive%\tech & tools files\process hacker\x64
%sysdrive%\cracking files & tweets\cracking files & tweets\process hacker\x64
%sysdrive%\cracking files & tweets\process hacker\x64
%profile%\onedrive\desktop\x64
%sysdrive%\itsuptoyou\tools for you\system tool\processhacker
%sysdrive%\process hacker 2
%sysdrive%\work station\service\processhacker-2.39-bin\x64
%sysdrive%\filehistory\jhk\main\data\c\users\jhk\desktop\jwk\img\wa\process hacker 2

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.

Windows 10 78.8%
Windows 7 12.1%
Windows 8.1 4.5%
Windows Server 2012 R2 3.0%
Windows Server 2008 R2 1.5%

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

ToolStatus.dll is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x0000adf0
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 241152

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

.text 77312 bytes · 32.1% of section data
MD5 7741781fea450a62665e493d244286f0
.rdata 49152 bytes · 20.4% of section data
MD5 ba4696381d192cc13554d9b946039338
.data 3072 bytes · 1.3% of section data
MD5 280e01704b32e78ed080e2c6bfee317c
.pdata 5120 bytes · 2.1% of section data
MD5 421d5d9e2d80b19c585c2a4102f083c8
.gfids 512 bytes · 0.2% of section data
Uncommon name
MD5 201992a1d7c2277c8e01c6f6b04a2c3c
.rsrc 103936 bytes · 43.1% of section data
MD5 4979b2dd173378012abe9105ccf11052
.reloc 2048 bytes · 0.8% of section data
MD5 283ed6e16ac02aea68c80cf972d0588e

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 3788efff135f8b17a179d02334d505e6.
  • 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. Use the Adware category to compare similar reports.