GridinSoft Threat Intelligence

PDown.dll file report

Under review File reputation report
MD5 5e22d9a7d0f556d7ea3310f3d995e376
Latest seen 2025-04-28 23:01:25 (a year ago)
First seen 2024-11-05 23:01:43 (2 years ago)
Size 224 KB
Publisher 360.cn
Product 360 升级库

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-11-05 23:01:43 (2 years ago); latest analysis 2025-04-28 23:01:25 (a year ago).

Publisher context

Company metadata: 360.cn. Product metadata: 360 升级库.

Digital signature

Signed by Chengdu Qilu 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.

PDown.dll is a Windows file recorded in the ThreatInfo database. It is associated with 360 升级库. The reported company name is 360.cn. The current detection status is Undefined, based on the latest analysis from 2025-04-28 23:01:25 (a year 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: 360 升级库
Company Name: 360.cn
MD5: 5e22d9a7d0f556d7ea3310f3d995e376
Size: 224 KB
First Published: 2024-11-05 23:01:43 (2 years ago)
Latest Published: 2025-04-28 23:01:25 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-04-28 23:01:25 (a year ago)
Signed By: Chengdu Qilu Technology Co. Ltd.
Status: Valid

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

ThreatInfo has observed PDown.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 100.0%

The most common operating system signal for PDown.dll 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.

PDown.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 0x00017716
Image base 0x10000000

PE Sections:

Sections 5
Raw data 220672

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

.text 164352 bytes · 74.5% of section data
MD5 2d8f7fed0c8b8111f3088253c7364f64
.rdata 32768 bytes · 14.8% of section data
MD5 2e0c2a47f9d2a6953cf22a32efb05c47
.data 10240 bytes · 4.6% of section data
MD5 4ab348991c5f14ef5455e7eb871fda91
.rsrc 2048 bytes · 0.9% of section data
MD5 fcfc4cc1eee0f6e3ed511652257a608a
.reloc 11264 bytes · 5.1% of section data
MD5 79b806cad30a0d79ed227fa112203e27

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 5e22d9a7d0f556d7ea3310f3d995e376.
  • 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.