WmBEnum.sys file report

MD5 5d410936831f7fb58eff941eac3f6d3d
Latest seen 2021-01-14 16:35:06 (5 years ago)
First seen 2020-12-10 06:27:13 (5 years ago)
Size 22 KB
Publisher Logitech Inc.
Signed by Logitech

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-12-10 06:27:13 (5 years ago); latest analysis 2021-01-14 16:35:06 (5 years ago).

Publisher context

Company metadata: Logitech Inc.. Product metadata: Logitech Gaming Software.

Digital signature

Signed by Logitech. 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.

WmBEnum.sys is a Windows file recorded in the ThreatInfo database. It is associated with Logitech Gaming Software. The reported company name is Logitech Inc.. The current detection status is Undefined, based on the latest analysis from 2021-01-14 16:35:06 (5 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: Logitech Gaming Software
Company Name: Logitech Inc.
MD5: 5d410936831f7fb58eff941eac3f6d3d
Size: 22 KB
First Published: 2020-12-10 06:27:13 (5 years ago)
Latest Published: 2021-01-14 16:35:06 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-14 16:35:06 (5 years ago)
Signed By: Logitech
Status: Valid

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

%profile%\dministrator\local settings\application data\slimware utilities inc\slimdrivers\backups\20181229t073710\root
%profile%\dministrator\local settings\application data\slimware utilities inc\slimdrivers\backups\20181231t072915687500\root
%profile%\dministrator\local settings\application data\slimware utilities inc\slimdrivers\backups\20181229t072053531250\root
%profile%\dministrator\local settings\application data\slimware utilities inc\slimdrivers\backups\20181229t072826609375\root
%localappdata%\slimware utilities inc\slimdrivers\backups\20200501t081141684142\root

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

80.0%
20.0%

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

Windows XP 80.0%
Windows 10 20.0%

The most common operating system signal for WmBEnum.sys is Windows XP with 80.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.

WmBEnum.sys is identified as pe for 32 systems. The subsystem is Native. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Native
PE Type: pe
OS Bitness: 32
Image Base: 0x00010000
Entry Address: 0x00002c61

PE Sections:

Name Size of data MD5
.text 5376 1276b30173d75857d12b00d98f3d03e8
.rdata 384 0d75ae7629d88fd4f77ab2f6c52ec5d9
.data 128 1f558917e0b83de44fffa4db41aab932
PAGE 4224 4967dcf00b2b0691f4950accfe16ca0f
INIT 1536 cacab202cda1428899eb803a84d13637
.rsrc 2560 0f4f744f5e715552121afeffc42d5e3f
.reloc 768 a0c6ede99708d42e1f2bd58511ee5896

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: