GridinSoft Threat Intelligence

PumaPlayer.dll file report

Under review File reputation report
MD5 d5aeb556be2d7bdbe09facf315d39b6b
Latest seen 2021-04-18 20:40:55 (5 years ago)
First seen 2021-04-18 20:40:55 (5 years ago)
Size 1 MB
Publisher 爱奇艺

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-04-18 20:40:55 (5 years ago); latest analysis 2021-04-18 20:40:55 (5 years ago).

Publisher context

Company metadata: 爱奇艺. Product metadata: 爱奇艺PPS影音.

Digital signature

Signed by BEIJING QIYI CENTURY SCIENCE&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.

PumaPlayer.dll is a Windows file recorded in the ThreatInfo database. It is associated with 爱奇艺PPS影音. The reported company name is 爱奇艺. The current detection status is Undefined, based on the latest analysis from 2021-04-18 20:40:55 (5 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: 爱奇艺PPS影音
Company Name: 爱奇艺
MD5: d5aeb556be2d7bdbe09facf315d39b6b
Size: 1 MB
First Published: 2021-04-18 20:40:55 (5 years ago)
Latest Published: 2021-04-18 20:40:55 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-04-18 20:40:55 (5 years ago)

The signature on PumaPlayer.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%\iqiyi video

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

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

PumaPlayer.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 0x0010e523
Image base 0x10000000

PE Sections:

Sections 5
Raw data 1502208

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

.text 1184256 bytes · 78.8% of section data
MD5 7e4c18a83fd4ef405cfb4fc45b2dac1c
.rdata 204800 bytes · 13.6% of section data
MD5 a87988241d9ad3fe20d47ed89184dbcc
.data 40960 bytes · 2.7% of section data
MD5 8ce85f309395e9ad7d12136f607c93ea
.rsrc 1536 bytes · 0.1% of section data
MD5 5fabded2b7ec4093367611acddf80064
.reloc 70656 bytes · 4.7% of section data
MD5 1f79bf75c3142db457bdd9efd6c7c130

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 d5aeb556be2d7bdbe09facf315d39b6b.
  • 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.