GridinSoft Threat Intelligence

PSUAInfo.dll file report

Clean record File reputation report
MD5 cd01fa439c51778ec801412e9e26bbf4
Latest seen 2021-07-26 20:34:00 (4 years ago)
First seen 2021-07-26 20:34:00 (4 years ago)
Size 537 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-07-26 20:34:00 (4 years ago); latest analysis 2021-07-26 20:34:00 (4 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.

PSUAInfo.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 2021-07-26 20:34:00 (4 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: cd01fa439c51778ec801412e9e26bbf4
Size: 537 KB
First Published: 2021-07-26 20:34:00 (4 years ago)
Latest Published: 2021-07-26 20:34:00 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-07-26 20:34:00 (4 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 PSUAInfo.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 PSUAInfo.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.

PSUAInfo.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 0x0004dd8c
Image base 0x10000000

PE Sections:

Sections 5
Raw data 531456

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

.text 333824 bytes · 62.8% of section data
MD5 97ea53a0bcf4807a0805fa4064f5c4a3
.rdata 161792 bytes · 30.4% of section data
MD5 cb595a85c7d104b73bc23f996fa7eab5
.data 9216 bytes · 1.7% of section data
MD5 0039b16cd774b8ae409067e6794a3508
.rsrc 7168 bytes · 1.3% of section data
MD5 cff0069e643d3e66f0feb23bd1175900
.reloc 19456 bytes · 3.7% of section data
MD5 b8ed806b5f4665f3cbdd548afa3f8ae1

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