GridinSoft Threat Intelligence

PSKMADLL.dll file report

Clean record File reputation report
MD5 73229ae9c25eac8692f49c1b8168760c
Latest seen 2021-07-26 20:31:56 (4 years ago)
First seen 2021-07-26 20:31:56 (4 years ago)
Size 69 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-07-26 20:31:56 (4 years ago); latest analysis 2021-07-26 20:31:56 (4 years ago).

Publisher context

Company metadata: Panda Security, S.L.. Product metadata: Panda Technologies.

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.

PSKMADLL.dll is a Windows file recorded in the ThreatInfo database. It is associated with Panda Technologies. 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:31:56 (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: Panda Technologies
Company Name: Panda Security, S.L.
MD5: 73229ae9c25eac8692f49c1b8168760c
Size: 69 KB
First Published: 2021-07-26 20:31:56 (4 years ago)
Latest Published: 2021-07-26 20:31:56 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-07-26 20:31:56 (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 PSKMADLL.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 PSKMADLL.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.

PSKMADLL.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 0x0000b870
Image base 0x10000000

PE Sections:

Sections 6
Raw data 55296

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

.text 44544 bytes · 80.6% of section data
MD5 7186fe7be9754dc32473310e6abff095
.rdata 4096 bytes · 7.4% of section data
MD5 370fdd7e1161c38ad58564eee4c00d77
.data 512 bytes · 0.9% of section data
MD5 24e4812dfb987c0957915d18972aad22
.PSMEM 512 bytes · 0.9% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1536 bytes · 2.8% of section data
MD5 185a18c3c9f05be6fe88bc8376196935
.reloc 4096 bytes · 7.4% of section data
MD5 3eca600c620f115f80bb29cd305295a4

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 73229ae9c25eac8692f49c1b8168760c.
  • 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.