GridinSoft Threat Intelligence

LGBusEnum.sys file report

Under review File reputation report
MD5 170e7093a77ad586f3a012a3db651d94
Latest seen 2021-01-14 16:30:29 (5 years ago)
First seen 2021-01-14 16:30:29 (5 years ago)
Size 19 KB
Signed by Logitech

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-14 16:30:29 (5 years ago); latest analysis 2021-01-14 16:30:29 (5 years ago).

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.

LGBusEnum.sys is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-01-14 16:30:29 (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.

MD5: 170e7093a77ad586f3a012a3db651d94
Size: 19 KB
First Published: 2021-01-14 16:30:29 (5 years ago)
Latest Published: 2021-01-14 16:30:29 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-14 16:30:29 (5 years ago)
Signed By: Logitech
Status: Valid

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

%localappdata%\slimware utilities inc\slimdrivers\backups\20200501t081141684142\root

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

Windows 10 100.0%

The most common operating system signal for LGBusEnum.sys 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.

LGBusEnum.sys is identified as pe for 32-bit 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.

Format pe
Architecture 32-bit
Subsystem Native
Entry point 0x00002161
Image base 0x00010000

PE Sections:

Sections 7
Raw data 11904

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

.text 1920 bytes · 16.1% of section data
MD5 2c8edde34df8d485316462cfd62eaff3
.rdata 384 bytes · 3.2% of section data
MD5 7c5524a1b994fa803fbdb652d7d72870
.data 256 bytes · 2.2% of section data
MD5 a7d96055a84d278871f1bc66026404c3
PAGE 4736 bytes · 39.8% of section data
Uncommon name
MD5 43cd7bd41a75e768d54ff85cea56dde7
INIT 1280 bytes · 10.8% of section data
Uncommon name
MD5 eab052bdcdf968964db53c4c8d8c186f
.rsrc 2688 bytes · 22.6% of section data
MD5 f338af0de77049bb8bdf03a9508bbe90
.reloc 640 bytes · 5.4% of section data
MD5 227bda101932691c65374ffbf7a27810

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 170e7093a77ad586f3a012a3db651d94.
  • 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.