GridinSoft Threat Intelligence

wrmntr.exe file report

Under review File reputation report
MD5 eb4df95a2cb5bc3720bc00c66bfee62a
Latest seen 2024-07-18 23:02:44 (2 years ago)
First seen 2023-11-22 23:30:43 (2 years ago)
Size 232 KB
Publisher WinRiser
Product WinRiser
Signed by Bit Guardian GmbH

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-11-22 23:30:43 (2 years ago); latest analysis 2024-07-18 23:02:44 (2 years ago).

Publisher context

Company metadata: WinRiser. Product metadata: WinRiser.

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.

wrmntr.exe is a Windows file recorded in the ThreatInfo database. It is associated with WinRiser. The reported company name is WinRiser. The current detection status is Undefined, based on the latest analysis from 2024-07-18 23:02:44 (2 years 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: WinRiser
Company Name: WinRiser
MD5: eb4df95a2cb5bc3720bc00c66bfee62a
Size: 232 KB
First Published: 2023-11-22 23:30:43 (2 years ago)
Latest Published: 2024-07-18 23:02:44 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-07-18 23:02:44 (2 years ago)
Signed By: Bit Guardian GmbH
Status: Valid

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

wrmntr.exe is identified as pe for -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 -bit
Subsystem Windows GUI
Entry point 0x0000297a
Image base 0x00400000

.NET Info:

MVID: 8fcfd10d-f2d6-47f4-dea9-18174b7e8a9f
Typelib ID: b6a81183-4966-4330-bdb5-17a5ed9ed34f

PE Sections:

Sections 3
Raw data 214528

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

.text 2560 bytes · 1.2% of section data
MD5 952dd6264b371f5b9bdca75b94ecce30
.reloc 512 bytes · 0.2% of section data
MD5 337fa77bcc36ff2ba893c344d5d28685
.rsrc 211456 bytes · 98.6% of section data
MD5 4f4cf9ee09da31f687b348df95b8b60c

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