LMouKE.sys file report

MD5 52550a3cdb1bee425569dee0a17e834a
Latest seen 2023-06-09 23:52:27 (2 years ago)
First seen 2017-05-29 04:07:59 (8 years ago)
Size 109 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:59 (8 years ago); latest analysis 2023-06-09 23:52:27 (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.

LMouKE.sys 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:52:27 (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: 52550a3cdb1bee425569dee0a17e834a
Size: 109 KB
First Published: 2017-05-29 04:07:59 (8 years ago)
Latest Published: 2023-06-09 23:52:27 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-06-09 23:52:27 (2 years ago)
Signed By: Logitech
Status: Valid

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

%programfiles%\drivertoolkit\download\eed543110b8a5f53ed1b08a6b3f60e0c\setpoint6.65.62_64\$_outdir\5-setpoint\cddrv3\setup
%programfiles%\drivertoolkit\download\eed543110b8a5f53ed1b08a6b3f60e0c\setpoint6.65.62_64\$_outdir\5-setpoint\cddrv3
%programfiles%\drivertoolkit\download\eed543110b8a5f53ed1b08a6b3f60e0c\setpoint6.65.62_64\$_outdir\5-setpoint\cddrv3
%programfiles%\drivertoolkit\download\eed543110b8a5f53ed1b08a6b3f60e0c\setpoint6.65.62_64\$_outdir\5-setpoint\cddrv3

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

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 LMouKE.sys 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.

LMouKE.sys is identified as pe for 64 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: 64
Image Base: 0x0000000000010000
Entry Address: 0x0001e310

PE Sections:

Name Size of data MD5
.text 64512 b4f071610673ea4955720b7c7b206abf
.rdata 13312 b7d64ae5ca3936f6b168d98d65105bf4
.data 12288 a80386df626f93ebeae0200442f65b0f
.pdata 5632 8d2b73be39d86cb2fc8ea85971e669bf
PAGE 2560 d5fe6a016eb637e87388abd5e117d35d
INIT 3584 ceb687a1e9754bcc4ba9a1a1fb7d4859
.rsrc 1536 aedf384eb1d4f02813f7b0e069cd3eec
.reloc 1024 5c0f5b3e040a74988c1be250f0af2ecd

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: