GridinSoft Threat Intelligence

wgmntr.exe file report

Under review File reputation report
MD5 06be6500f49ccdfdeb2be589988f249b
Latest seen 2026-02-11 23:01:44 (3 months ago)
First seen 2026-02-11 23:01:40 (3 months ago)
Size 243 KB
Publisher Bit Guardian
Product Win Guardian
Signed by Bit Guardian GmbH

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2026-02-11 23:01:40 (3 months ago); latest analysis 2026-02-11 23:01:44 (3 months ago).

Publisher context

Company metadata: Bit Guardian. Product metadata: Win Guardian.

Digital signature

Signed by Bit Guardian GmbH. 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.

wgmntr.exe is a Windows file recorded in the ThreatInfo database. It is associated with Win Guardian. The reported company name is Bit Guardian. The current detection status is Undefined, based on the latest analysis from 2026-02-11 23:01:44 (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.

Product Name: Win Guardian
Company Name: Bit Guardian
MD5: 06be6500f49ccdfdeb2be589988f249b
Size: 243 KB
First Published: 2026-02-11 23:01:40 (3 months ago)
Latest Published: 2026-02-11 23:01:44 (3 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-02-11 23:01:44 (3 months ago)
Signed By: Bit Guardian GmbH
Status: Valid

The signature on wgmntr.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 wgmntr.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 8.1 100.0%

The most common operating system signal for wgmntr.exe is Windows 8.1 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.

wgmntr.exe 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 0x00002972
Image base 0x00400000

.NET Info:

MVID: 8c6e3f92-14ec-4df4-6f18-e2463fb14a84
Typelib ID: b6a81183-4966-4330-bdb5-17a5ed9ed34f

PE Sections:

Sections 3
Raw data 231424

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

.text 2560 bytes · 1.1% of section data
MD5 84e10e96abf2ddc3f0f42b5e8d11ba60
.reloc 512 bytes · 0.2% of section data
MD5 3c70857c2033323c1bbe8795f09891b6
.rsrc 228352 bytes · 98.7% of section data
MD5 bfe06e61557adf199fc28312787caa7c

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 06be6500f49ccdfdeb2be589988f249b.
  • 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.