GridinSoft Threat Intelligence

PSNComms.dll file report

Clean record File reputation report
MD5 966a9a30a757bd0bf9c533b7a31c5d98
Latest seen 2024-01-06 23:09:42 (2 years ago)
First seen 2024-01-06 23:09:42 (2 years ago)
Size 140 KB
Product Consumer Common

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2024-01-06 23:09:42 (2 years ago); latest analysis 2024-01-06 23:09:42 (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.

PSNComms.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:09:42 (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: 966a9a30a757bd0bf9c533b7a31c5d98
Size: 140 KB
First Published: 2024-01-06 23:09:42 (2 years ago)
Latest Published: 2024-01-06 23:09:42 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-01-06 23:09:42 (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 PSNComms.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 PSNComms.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.

PSNComms.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 0x00016c12
Image base 0x10000000

PE Sections:

Sections 5
Raw data 128000

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

.text 94208 bytes · 73.6% of section data
MD5 b02b36f1a53e2740ca56852693ee8184
.rdata 22528 bytes · 17.6% of section data
MD5 9f59a49390c9618260d6f2c0b364d22d
.data 1024 bytes · 0.8% of section data
MD5 e5cbd249a269104e4edf47e747ec71fe
.rsrc 1536 bytes · 1.2% of section data
MD5 657971323f6087e1e2fbf201154032a7
.reloc 8704 bytes · 6.8% of section data
MD5 95bd46bceac496ed3565526eeb2aab1a

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 966a9a30a757bd0bf9c533b7a31c5d98.
  • 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.