GridinSoft Threat Intelligence

PSUAShell.dll file report

Clean record File reputation report
MD5 99f8fb277517507a6b771336884138d8
Latest seen 2024-01-06 23:14:43 (2 years ago)
First seen 2021-07-26 20:26:45 (4 years ago)
Size 245 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-07-26 20:26:45 (4 years ago); latest analysis 2024-01-06 23:14:43 (2 years ago).

Publisher context

Company metadata: Panda Security, S.L.. Product metadata: Consumer Product.

Digital signature

Signed by Panda Security S.L.. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

PSUAShell.dll is a Windows file recorded in the ThreatInfo database. It is associated with Consumer Product. The reported company name is Panda Security, S.L.. The current detection status is Clean, based on the latest analysis from 2024-01-06 23:14:43 (2 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Consumer Product
Company Name: Panda Security, S.L.
MD5: 99f8fb277517507a6b771336884138d8
Size: 245 KB
First Published: 2021-07-26 20:26:45 (4 years ago)
Latest Published: 2024-01-06 23:14:43 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-01-06 23:14:43 (2 years ago)
Signed By: Panda Security S.L.
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%programfiles%\telmex

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

PSUAShell.dll is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x00013d34
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 234496

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

.text 143872 bytes · 61.4% of section data
MD5 307876f71edab75a5f37300e0acaef4b
.rdata 62976 bytes · 26.9% of section data
MD5 8ee71330c03eb528fd2cb5e456c0e2a9
.data 10240 bytes · 4.4% of section data
MD5 364bf5a29a2e6f328850a536de8ecc46
.pdata 8192 bytes · 3.5% of section data
MD5 f7236089643052c6612558fafcc56055
.rsrc 6144 bytes · 2.6% of section data
MD5 7ddb51c703fb6c029de897106c0fa973
.reloc 3072 bytes · 1.3% of section data
MD5 467024201165a8a435aaa53e99a8261a

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 99f8fb277517507a6b771336884138d8.
  • 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.