GridinSoft Threat Intelligence

PSNReg.dll file report

Clean record File reputation report
MD5 28ac574b550ce9b84b2813276ab0a1ad
Latest seen 2024-01-06 23:16:12 (2 years ago)
First seen 2021-07-26 20:30:56 (4 years ago)
Size 51 KB
Product Consumer Common

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-07-26 20:30:56 (4 years ago); latest analysis 2024-01-06 23:16:12 (2 years ago).

Publisher context

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

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.

PSNReg.dll is a Windows file recorded in the ThreatInfo database. It is associated with Consumer Common. 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:16:12 (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 Common
Company Name: Panda Security, S.L.
MD5: 28ac574b550ce9b84b2813276ab0a1ad
Size: 51 KB
First Published: 2021-07-26 20:30:56 (4 years ago)
Latest Published: 2024-01-06 23:16:12 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-01-06 23:16:12 (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 PSNReg.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 PSNReg.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.

PSNReg.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 0x00007014
Image base 0x30350000

PE Sections:

Sections 5
Raw data 36864

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

.text 26624 bytes · 72.2% of section data
MD5 0f20996d0a67d45f0b44c8155e676a0c
.rdata 5120 bytes · 13.9% of section data
MD5 a03ec9d4fc14727cfa5a6cba0aa3e188
.data 512 bytes · 1.4% of section data
MD5 8409315731500cd5e20c31f768f55a18
.rsrc 1536 bytes · 4.2% of section data
MD5 1abd85146e9829e8c0e6f1f74ad9d370
.reloc 3072 bytes · 8.3% of section data
MD5 d5b6ac2a43229e21ebfc719241a20440

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 28ac574b550ce9b84b2813276ab0a1ad.
  • 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.