GridinSoft Threat Intelligence

lmd.dll file report

Under review File reputation report
MD5 70298560b1ae315300511fd2d7fc0b79
Latest seen 2024-03-22 23:01:00 (2 years ago)
First seen 2018-07-27 05:05:40 (7 years ago)
Size 69 KB
Product 暴风影音5

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-07-27 05:05:40 (7 years ago); latest analysis 2024-03-22 23:01:00 (2 years ago).

Publisher context

Company metadata: 暴风集团股份有限公司. Product metadata: 暴风影音5.

Digital signature

Signed by 暴风集团股份有限公司. 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.

lmd.dll is a Windows file recorded in the ThreatInfo database. It is associated with 暴风影音5. The reported company name is 暴风集团股份有限公司. The current detection status is Undefined, based on the latest analysis from 2024-03-22 23:01:00 (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: 暴风影音5
Company Name: 暴风集团股份有限公司
MD5: 70298560b1ae315300511fd2d7fc0b79
Size: 69 KB
First Published: 2018-07-27 05:05:40 (7 years ago)
Latest Published: 2024-03-22 23:01:00 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-03-22 23:01:00 (2 years ago)
Signed By: 暴风集团股份有限公司
Status: Valid

The signature on lmd.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%\baofeng\stormplayer

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

Windows 10 80.8%
Windows 7 11.5%
Windows 8.1 7.7%

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

lmd.dll 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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x0000a351
Image base 0x10000000

PE Sections:

Sections 5
Raw data 64000

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

.text 41984 bytes · 65.6% of section data
MD5 fab613b1f3da32682afdb3f51e24cd3b
.rdata 14336 bytes · 22.4% of section data
MD5 5a78d6383d907b73fb095b72b8fd2984
.data 1536 bytes · 2.4% of section data
MD5 ea695d9a4a87a9f67c2132cbc8afa4c4
.rsrc 1536 bytes · 2.4% of section data
MD5 99890a6b631665c0a24215ce2b393b59
.reloc 4608 bytes · 7.2% of section data
MD5 ff68844bc95c02cb0a7d07b0a7e9ee27

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 70298560b1ae315300511fd2d7fc0b79.
  • 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.