GridinSoft Threat Intelligence
LMS.exe file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2022-11-01 23:58:11 (3 years ago); latest analysis 2022-11-01 23:58:11 (3 years ago).
Company metadata: Intel Corporation. Product metadata: Intel(R) Management and Security Application Local Management Service.
Signed by Intel(R) Embedded Subsystems and IP Blocks Group;Microsoft Windows Hardware Compatibility Publisher. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
LMS.exe is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) Management and Security Application Local Management Service. The reported company name is Intel Corporation. The current detection status is Undefined, based on the latest analysis from 2022-11-01 23:58:11 (3 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.
File Details
| Product Name: | Intel(R) Management and Security Application Local Management Service |
| Company Name: | Intel Corporation |
| MD5: | 8da82888bc2144c94ba784bafb57f042 |
| Size: | 3 MB |
| First Published: | 2022-11-01 23:58:11 (3 years ago) |
| Latest Published: | 2022-11-01 23:58:11 (3 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2022-11-01 23:58:11 (3 years ago) |
Overview
| Signed By: | Intel(R) Embedded Subsystems and IP Blocks Group;Microsoft Windows Hardware Compatibility Publisher |
| Status: | Valid |
The signature on LMS.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.
Common Places:
| %system%\driverstore\filerepository |
ThreatInfo has observed LMS.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.
Geographic signal
Observed country distribution
ThreatInfo has seen LMS.exe across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for LMS.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.
Analysis
LMS.exe is identified as pe for 32-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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
f4ae3830aaf47bf1d8e77238fca664be
e31df8f973893219bbc7cbf82e3652c2
3fabed9ffc1d4280c09eacc6dc0cd657
21926232cbb0815cec016ce1474a1248
143744fe82c6745f2c169e48a1fae082
99235b02a44e0c53ff2276e4de5b2b13
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.