GridinSoft Threat Intelligence
QMDlder.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.
First seen 2020-08-08 18:44:38 (5 years ago); latest analysis 2021-03-01 04:32:36 (5 years ago).
Company metadata: Tencent. Product metadata: PC Manager.
Signed by Tencent Technology(Shenzhen) Company Limited. The signature is not reported as trusted and valid, which can indicate tampering, repackaging, or copied publisher data.
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
QMDlder.dll is a Windows file recorded in the ThreatInfo database. It is associated with PC Manager. The reported company name is Tencent. The current detection status is Undefined, based on the latest analysis from 2021-03-01 04:32:36 (5 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.
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: | PC Manager |
| Company Name: | Tencent |
| MD5: | 216199fffdbb325bd2341c418d611a98 |
| Size: | 130 KB |
| First Published: | 2020-08-08 18:44:38 (5 years ago) |
| Latest Published: | 2021-03-01 04:32:36 (5 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-03-01 04:32:36 (5 years ago) |
Overview
| Signed By: | Tencent Technology(Shenzhen) Company Limited |
| Status: | Invalid (digital signature could be stolen or file could be patched) |
The signature on QMDlder.dll is not reported as trusted and valid. Invalid or suspicious signature data can indicate tampering, repackaging, or an unrelated file using copied publisher information.
Common Places:
| %programfiles%\tencent\qqpcmgr |
ThreatInfo has observed QMDlder.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.
Geographic signal
Observed country distribution
ThreatInfo has seen QMDlder.dll across 3 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Poland with 33.3% 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 QMDlder.dll is Windows 10 with 66.7% 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
QMDlder.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
ebc7efe9515d146180b60cd76975caee
05ef52ca46cda3d7e73cda787f110e36
c7da8b9ce64878fdcb7a9f85feb55e35
c729e574c592e1f65fb61acc69065819
6bac974d3ef6f08e6de4703b2bd06f04
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.