PCTcore64.sys - Vulnerable (78/100) - DriverShield Analysis

Analysis of PCTcore64.sys: vulnerable verdict, risk score 78/100. 4 YARA matches, 8/75 multi-engine detections. SHA256 c76dd87891e3e30d. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

PCTcore64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver PCTcore64.sys and assigned a verdict of Vulnerable with a composite risk score of 78/100, indicating a known or likely vulnerability surface (60-79 band).

VerdictVulnerable (78/100)
YARA matches4
Multi-engine detections8 / 75
File size233488 bytes
Code-signing signerVeriSign Time Stamping Services Signer - G2
Analyzed2026-09-06
SHA256c76dd87891e3e30db2aed057e7b04c19ca264f434c21f68a7a2d9b17a97aff39
SHA1d5609dc8c5215ebe197aad74ea1459a38f3612dd
MD560f19af0a9a26851ad9bc2d981afbac6

Driver identity

Version resource data embedded in the PCTcore64.sys PE header, as extracted by the analysis engine.

File descriptionPC Tools KDS Core Driver
ProductKernel Driver Suite
CompanyPC Tools
Original filenamePCTCore.sys
Internal namePCTCore.sys
File version2.0.0.37 built by: WinDDK
CopyrightCopyright (c) 2010 PC Tools. All rights reserved.

How the 78/100 score breaks down

Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.

ComponentSub-score
Multi-engine consensus0 / 100
YARA signature matches100 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface100 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (39)

Kernel-mode APIs resolved from the Import Address Table of PCTcore64.sys, ranked by exploitation relevance.

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutinehighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateThreadNotifyRoutinemediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
CmRegisterCallbackExmediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
CmRegisterCallbackmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
ZwWriteFilemediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
RtlInitUnicodeStringlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
ProbeForReadlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 39 resolved.

IOCTL dispatch codes (40)

Control codes reachable through the driver dispatch routine. Codes tied to published exploit code are flagged, since they are the primary Bring Your Own Vulnerable Driver (BYOVD) entry points.

CodeSeverityTransferDescription
0x00221843highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #1552
0x0080858BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #354
0x00808D8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #866
0x0080850FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #323
0x00808F8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #994
0x0080840FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #259
0x0022341FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3335
0x0080928BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1186
0x0080888BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #546
0x00801043highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1040
0x0080BAFFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3775
0x0022BEC3highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #4016
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00809B39mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1742
0x008024B4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2349
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x00229885mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1569
0x00221885mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1569
0x008024A4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2345
0x0022BA78mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3742

Showing 24 of 40 extracted control codes.

PE sections

Section layout and Shannon entropy. High entropy in a code section is a packing or encryption indicator.

SectionVirtual sizeRaw sizeEntropyFlags
.text0x181BD0x182006.52CODE, EXEC, READ
.rdata0x3EE40x40007IDATA, READ
.data0x0AFC0x04001.27IDATA, READ, WRITE
.pdata0x0E280x10004.97IDATA, READ
PAGE0x144A10x146006.36CODE, EXEC, READ
INIT0x3D400x3E006.1CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x0D580x0E003.33IDATA, READ, DISCARD
.reloc0x021C0x04000.81IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLRNot enabled
DEPNot enabled
Integrity checkNot enforced
Mitigation score5 / 100

YARA rule matches (4)

RuleSeverityDetects
PUA_VULN_Driver_Pctools_Pctcoresys_Kerneldriversuite_C76DmediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - PCTcore64.sys, PCTCore64.sys. Investigate matches in context: expected filen...
BYOVD_ProcKillcriticalProcess termination EDR killer
SUSP_CallbacksmediumKernel callback registration
MAL_EDRKillercriticalGeneric EDR killer pattern

MITRE ATT&CK techniques (17)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1014RootkitDefense Evasion
T1055.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerVeriSign Time Stamping Services Signer - G2
Signer organisationVeriSign, Inc.
IssuerVeriSign Time Stamping Services CA
Serial3825D7FAF861AF9EF490E726B5D65AD5
Valid from2007-06-15 00:00 UTC
Valid until2012-06-14 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 100 paths explored at a maximum depth of 100. Vulnerability classes reached: 0. Exploitable paths: 3.

Corpus match: this hash is present in the known-vulnerable driver corpus DriverShield cross-references during analysis, which is why the score carries a full weighting on that component.

Frequently asked questions about PCTcore64.sys

Is PCTcore64.sys safe?

Based on DriverShield static and dynamic analysis, PCTcore64.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 78/100 (verdict: vulnerable). Always validate findings independently before acting.

What is the risk score of PCTcore64.sys?

PCTcore64.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: c76dd87891e3e30db2aed057e7b04c19ca264f434c21f68a7a2d9b17a97aff39.

What is PCTcore64.sys?

PCTcore64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by VeriSign Time Stamping Services Signer - G2.

Related: Other drivers signed by VeriSign Time Stamping Services Signer - G2 · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact