GridinSoft Threat Intelligence

PCPElam64.sys file report

Clean record File reputation report
MD5 22c8b8ef9fc04d61e63ca7a0e0eb4886
Latest seen 2023-09-06 23:12:47 (2 years ago)
First seen 2020-03-28 19:30:33 (6 years ago)
Size 17 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-03-28 19:30:33 (6 years ago); latest analysis 2023-09-06 23:12:47 (2 years ago).

Digital signature

Signed by Microsoft Windows Early Launch Anti-malware Publisher. 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.

PCPElam64.sys is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2023-09-06 23:12:47 (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.

MD5: 22c8b8ef9fc04d61e63ca7a0e0eb4886
Size: 17 KB
First Published: 2020-03-28 19:30:33 (6 years ago)
Latest Published: 2023-09-06 23:12:47 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-09-06 23:12:47 (2 years ago)
Signed By: Microsoft Windows Early Launch Anti-malware Publisher
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%\pcpitstop

ThreatInfo has observed PCPElam64.sys 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 92.9%
Windows 7 7.1%

The most common operating system signal for PCPElam64.sys is Windows 10 with 92.9% 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.

PCPElam64.sys is identified as pe for 64-bit systems. The subsystem is Native. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 64-bit
Subsystem Native
Entry point 0x00001330
Image base 0x0000000140000000

PE Sections:

Sections 7
Raw data 8704

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

.text 3584 bytes · 41.2% of section data
MD5 a37c91702b9217ea168926bbecfb2598
.rdata 1536 bytes · 17.6% of section data
MD5 9d20bdd98879032b43ca53d80b90347a
.data 512 bytes · 5.9% of section data
MD5 433cf124e73e660bdced145675678ebc
.pdata 512 bytes · 5.9% of section data
MD5 9c77d57f52cc9c64c4d04c00ec068115
INIT 1024 bytes · 11.8% of section data
Uncommon name
MD5 12ec996bd4830c73806378219913a9e2
.rsrc 1024 bytes · 11.8% of section data
MD5 b724430b0e6bbe7b2aff00c8dda76e67
.reloc 512 bytes · 5.9% of section data
MD5 4cd4d452136bad59681121a50b3fe814

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 22c8b8ef9fc04d61e63ca7a0e0eb4886.
  • 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.