GridinSoft Threat Intelligence

Pop.dll file report

Under review File reputation report
MD5 5649b990af5d1f248cdebc2417dd8e9f
Latest seen 2024-09-08 23:01:07 (2 years ago)
First seen 2019-03-11 05:27:20 (7 years ago)
Size 545 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-03-11 05:27:20 (7 years ago); latest analysis 2024-09-08 23:01:07 (2 years ago).

Publisher context

Product metadata: 鲁大师升级模块.

Digital signature

Signed by Beijing Qihu Technology Co., Ltd.. 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.

Pop.dll is a Windows file recorded in the ThreatInfo database. It is associated with 鲁大师升级模块. The current detection status is Undefined, based on the latest analysis from 2024-09-08 23:01:07 (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: 鲁大师升级模块
MD5: 5649b990af5d1f248cdebc2417dd8e9f
Size: 545 KB
First Published: 2019-03-11 05:27:20 (7 years ago)
Latest Published: 2024-09-08 23:01:07 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-09-08 23:01:07 (2 years ago)
Signed By: Beijing Qihu Technology Co., Ltd.
Status: Valid

The signature on Pop.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%\ludashi\ludashi
%programfiles%\ludashi
%appdata%\360bizhi
%programfiles%\ldslite

ThreatInfo has observed Pop.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 88.0%
Windows 7 12.0%

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

Pop.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 0x0003e8de
Image base 0x10000000

PE Sections:

Sections 5
Raw data 542208

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

.text 402432 bytes · 74.2% of section data
MD5 6806669d36425a6a554d8da94bdc2212
.rdata 94208 bytes · 17.4% of section data
MD5 a957b8607446e13fb45fb75dc792866b
.data 18944 bytes · 3.5% of section data
MD5 4dea12f724ada6f091223473df16541f
.rsrc 2048 bytes · 0.4% of section data
MD5 1563bdc2aec07802159e3e00fbd3b6e3
.reloc 24576 bytes · 4.5% of section data
MD5 5a01df5eb341f42ae4444c754c82729f

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 5649b990af5d1f248cdebc2417dd8e9f.
  • 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.