terminpt.sys - Clean (20/100) - DriverShield Analysis

Analysis of terminpt.sys: clean verdict, risk score 20/100. 0 YARA matches. SHA256 6f88375dd12a648b. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

terminpt.sys - Analysis Report

DriverShield analyzed the Windows kernel driver terminpt.sys and assigned a verdict of Clean with a composite risk score of 20/100, indicating no notable risk signals (0-29 band).

VerdictClean (20/100)
YARA matches0
File size41272 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-03-22
SHA2566f88375dd12a648b77bb6eb4be527ff6678ee76a2059db5b4cc971cdb31d0db8
SHA1f8895f02b9218f682f6574f1631f576820b1df07
MD5c225b94f2b27ac97c3e66c0550aea249

Driver identity

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

File descriptionTerminal Server Input Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenameterminpt.sys
Internal nameterminpt.sys
File version10.0.19041.1 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 20/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 matches0 / 100
Dangerous kernel imports75 / 100
IOCTL dispatch surface18 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (15)

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

APIRiskWhy it matters
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ObOpenObjectByPointermediumModerate risk - system modification capability
KeWaitForSingleObjectlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign

IOCTL dispatch codes (6)

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
0x0034E72DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2507
0x0034C32DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #203
0x00220F3DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #975
0x00808789mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #482
0x003403A0mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #232

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x24E90x26005.95CODE, EXEC, READ
.rdata0x08700x0A004.26IDATA, READ
.data0x02400x02001.11IDATA, READ, WRITE
.pdata0x02DC0x04003.19IDATA, READ
.idata0x09020x0A004.13IDATA, READ
PAGE0x29170x2A006.06CODE, EXEC, READ
INIT0x04A20x06005.06CODE, EXEC, READ, DISCARD
GFIDS0x00600x02000.86IDATA, READ, DISCARD
.rsrc0x04100x06002.43IDATA, READ, DISCARD
.reloc0x030C0x04004.34IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score85 / 100

MITRE ATT&CK techniques (6)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
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

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial330000023241FB59996DCC4DFF000000000232
Valid from2019-05-02 21:24 UTC
Valid until2020-05-02 21:24 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about terminpt.sys

Is terminpt.sys safe?

Based on DriverShield static and dynamic analysis, terminpt.sys is assessed as clean, with no notable risk signals. Its composite risk score is 20/100 (verdict: clean). Always validate findings independently before acting.

What is the risk score of terminpt.sys?

terminpt.sys has a DriverShield composite risk score of 20/100, placing it in the clean verdict band. SHA256: 6f88375dd12a648b77bb6eb4be527ff6678ee76a2059db5b4cc971cdb31d0db8.

What is terminpt.sys?

terminpt.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Microsoft Windows.

Related: Other drivers signed by Microsoft Windows · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact