GridinSoft Threat Intelligence

pknspam.dll file report

Clean record File reputation report
MD5 3f08c4e5fb9e916b76eabef5cff3a36c
Latest seen 2024-01-06 23:23:56 (2 years ago)
First seen 2021-07-26 20:24:49 (4 years ago)
Size 198 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

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

Publisher context

Company metadata: Panda Security, S.L.. Product metadata: Panda Anti-Malware.

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.

pknspam.dll is a Windows file recorded in the ThreatInfo database. It is associated with Panda Anti-Malware. 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:23: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: Panda Anti-Malware
Company Name: Panda Security, S.L.
MD5: 3f08c4e5fb9e916b76eabef5cff3a36c
Size: 198 KB
First Published: 2021-07-26 20:24:49 (4 years ago)
Latest Published: 2024-01-06 23:23:56 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-01-06 23:23: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 pknspam.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 pknspam.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.

pknspam.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 0x0001b7b0
Image base 0x10000000

PE Sections:

Sections 5
Raw data 185856

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

.text 122880 bytes · 66.1% of section data
MD5 be657233de0a7cb4002a00bf6fae6a3e
.rdata 38912 bytes · 20.9% of section data
MD5 24a1d16905cb73368b4ac1984e5e933b
.data 5120 bytes · 2.8% of section data
MD5 3c19146f78b773ab33252a65fd25bcb9
.rsrc 1536 bytes · 0.8% of section data
MD5 c950617b76bcefb568190cfdcbb2d256
.reloc 17408 bytes · 9.4% of section data
MD5 8c0770a6064e10e6e844b2bb8f3294bc

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 3f08c4e5fb9e916b76eabef5cff3a36c.
  • 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.