GridinSoft Threat Intelligence

PSUAMain.exe file report

Clean record File reputation report
MD5 74a27011c122ceacf81f65e3dfbf7968
Latest seen 2024-01-06 23:24:56 (2 years ago)
First seen 2021-07-26 20:46:02 (4 years ago)
Size 164 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-07-26 20:46:02 (4 years ago); latest analysis 2024-01-06 23:24:56 (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.

PSUAMain.exe 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:24:56 (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: 74a27011c122ceacf81f65e3dfbf7968
Size: 164 KB
First Published: 2021-07-26 20:46:02 (4 years ago)
Latest Published: 2024-01-06 23:24:56 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-01-06 23:24:56 (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 PSUAMain.exe 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 PSUAMain.exe 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.

PSUAMain.exe 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 0x0000c174
Image base 0x00400000

PE Sections:

Sections 5
Raw data 147456

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

.text 49152 bytes · 33.3% of section data
MD5 99c11b918a37578d360e955cc2f7d4e5
.rdata 90112 bytes · 61.1% of section data
MD5 d257f90be0b76557e80e21c15ff814ba
.data 512 bytes · 0.3% of section data
MD5 63fc4419170446230f3f0da56240e120
.rsrc 3584 bytes · 2.4% of section data
MD5 9f25c80a62854921988d107bfb15fb39
.reloc 4096 bytes · 2.8% of section data
MD5 b0486de33e04c74d4f550472aea64166

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 74a27011c122ceacf81f65e3dfbf7968.
  • 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.