GridinSoft Threat Intelligence

WD.Diag.exe file report

Under review File reputation report
MD5 ff60e6d8b2c1268f3b2617d31a1938bf
Latest seen 2026-02-07 23:01:14 (3 months ago)
First seen 2024-02-23 23:31:13 (2 years ago)
Size 155 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-02-23 23:31:13 (2 years ago); latest analysis 2026-02-07 23:01:14 (3 months ago).

Digital signature

Signed by WATCHDOGDEVELOPMENT.COM, LLC. 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.

WD.Diag.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2026-02-07 23:01:14 (3 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.

MD5: ff60e6d8b2c1268f3b2617d31a1938bf
Size: 155 KB
First Published: 2024-02-23 23:31:13 (2 years ago)
Latest Published: 2026-02-07 23:01:14 (3 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-02-07 23:01:14 (3 months ago)
Signed By: WATCHDOGDEVELOPMENT.COM, LLC
Status: Valid

The signature on WD.Diag.exe 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%

ThreatInfo has observed WD.Diag.exe 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 100.0%

The most common operating system signal for WD.Diag.exe 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.

WD.Diag.exe is identified as pe for 64-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x00011b50
Image base 0x0000000140000000

PE Sections:

Sections 7
Raw data 139776

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

.text 90624 bytes · 64.8% of section data
MD5 4bc4bf2ba56ec297fec613d3683769cc
.rdata 38400 bytes · 27.5% of section data
MD5 b6d594b5b0793ef4f0f4d77b176c6c28
.data 2560 bytes · 1.8% of section data
MD5 b21924c207f371aa17353377f5b9b2aa
.pdata 5120 bytes · 3.7% of section data
MD5 6e50daca5d45ef69ef982ae6f5a9c104
_RDATA 512 bytes · 0.4% of section data
Uncommon name
MD5 b43e8d95141b95138722c961306f9918
.reloc 1024 bytes · 0.7% of section data
MD5 84a72bc8b1aee292ec0e681b14cb9100
.rsrc 1536 bytes · 1.1% of section data
MD5 ca1842a8e7c787474346ef07d121cb78

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 ff60e6d8b2c1268f3b2617d31a1938bf.
  • 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.