ipctype.sys - Vulnerable (72/100) - DriverShield Analysis

Analysis of ipctype.sys: vulnerable verdict, risk score 72/100. 2 YARA matches, 0/73 multi-engine detections. SHA256 8e2acce10d704c8b. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

ipctype.sys - Analysis Report

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

VerdictVulnerable (72/100)
YARA matches2
Multi-engine detections0 / 73
File size14096 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-04-02
SHA2568e2acce10d704c8b511c8b6211a2be5d8e4ade91ebcbda2ac10018e4c0ae99fb
SHA196611a3d59ea7df9453e194fb7c19d0f944bcefc
MD5c8f6cd1c989f364f126e6855f1178704

Driver identity

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

File descriptionIPCType Device Driver for 64bit
ProductIPCType Device Driver for 64bit
CompanyDigital Electronics Corporation
Original filenameipctype.sys
Internal nameipctype.sys
File version1.0.2.0
CopyrightCopyright (C) 2013 Digital Electronics Corporation. All Rights Reserved.

How the 72/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 matches80 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface12 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (12)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
KeBugCheckExmediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ExFreePoollowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign

IOCTL dispatch codes (4)

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
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x008010B9mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1070
0x00340398mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #230
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x04E80x06005.08CODE, EXEC, READ
.rdata0x018C0x02003.49IDATA, READ
.data0x01180x02000.3IDATA, READ, WRITE
.pdata0x00540x02000.77IDATA, READ
INIT0x02CA0x04003.97CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03F80x04003.28IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (2)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (11)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003OS Credential DumpingCredential Access
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1006Direct Volume AccessDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerSymantec Time Stamping Services CA - G2
Signer organisationSymantec Corporation
IssuerThawte Timestamping CA
Serial7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from2012-12-21 00:00 UTC
Valid until2020-12-30 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about ipctype.sys

Is ipctype.sys safe?

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

What is the risk score of ipctype.sys?

ipctype.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 8e2acce10d704c8b511c8b6211a2be5d8e4ade91ebcbda2ac10018e4c0ae99fb.

What is ipctype.sys?

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

Related: Other drivers signed by Symantec Time Stamping Services CA - 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