LBTServ.dll file report

MD5 13c6ca60faedd3373c8ea2d834f482a1
Latest seen 2023-06-09 23:55:48 (2 years ago)
First seen 2017-05-29 04:07:55 (8 years ago)
Size 129 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 2017-05-29 04:07:55 (8 years ago); latest analysis 2023-06-09 23:55:48 (2 years ago).

Publisher context

Company metadata: Logitech, Inc.. Product metadata: Logitech SetPoint.

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.

LBTServ.dll is a Windows file recorded in the ThreatInfo database. It is associated with Logitech SetPoint. The reported company name is Logitech, Inc.. The current detection status is Undefined, based on the latest analysis from 2023-06-09 23:55:48 (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: Logitech SetPoint
Company Name: Logitech, Inc.
MD5: 13c6ca60faedd3373c8ea2d834f482a1
Size: 129 KB
First Published: 2017-05-29 04:07:55 (8 years ago)
Latest Published: 2023-06-09 23:55:48 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-06-09 23:55:48 (2 years ago)
Signed By: Logitech
Status: Valid

The signature on LBTServ.dll 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%\drivertoolkit\download\eed543110b8a5f53ed1b08a6b3f60e0c\setpoint6.65.62_64\$_outdir\5-setpoint\cddrv3\setup\$shell[127]\logishrd\bluetooth
%programfiles%\drivertoolkit\download\eed543110b8a5f53ed1b08a6b3f60e0c\setpoint6.65.62_64\$_outdir\5-setpoint\cddrv3\setup\$shell[127]\logishrd
%programfiles%\drivertoolkit\download\eed543110b8a5f53ed1b08a6b3f60e0c\setpoint6.65.62_64\$_outdir\5-setpoint\cddrv3\setup\$shell[127]\logishrd
%programfiles%\drivertoolkit\download\eed543110b8a5f53ed1b08a6b3f60e0c\setpoint6.65.62_64\$_outdir\5-setpoint\cddrv3\setup\$shell[127]\logishrd

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

12.5%
12.5%
12.5%
12.5%
12.5%
12.5%
12.5%
12.5%

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

Windows 10 87.5%
Windows 7 12.5%

The most common operating system signal for LBTServ.dll is Windows 10 with 87.5% 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.

LBTServ.dll is identified as pe for 32 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x10000000
Entry Address: 0x0000cec3

PE Sections:

Name Size of data MD5
.text 90112 42c9640d620e0848645f080a35ed1f45
.rdata 17920 13fc0a9059260ac3f4fb49ae55d33036
.data 5632 53fbc573558011f2e85a89b963a52a80
.rsrc 2048 382865e8e3906d66881f1bc61c73d907
.reloc 9728 16efa97238e6f37fedb223ffaa4ee252

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: