HtcVComV64.sys - Clean (24/100) - DriverShield Analysis

Analysis of HtcVComV64.sys: clean verdict, risk score 24/100. 0 YARA matches, 0/76 multi-engine detections. SHA256 4cf12851a5a45917. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

HtcVComV64.sys - Analysis Report

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

VerdictClean (24/100)
YARA matches0
Multi-engine detections0 / 76
File size121800 bytes
Code-signing signerSqa.com(Test)
Analyzed2026-04-01
SHA2564cf12851a5a45917c3a9139b19d79434f2038611b617f83a714506cc7a1a6c61
SHA17b34ff5bfdab5c726654021439987d3248189eab
MD57c7c986776d00e575bfbde5dcbdc615d

Driver identity

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

File descriptionUSB Modem/Serial Device Driver
ProductQUALCOMM Incorporated USB Modem/Serial Device Driver
CompanyQUALCOMM Incorporated
Original filenameqcusbser.sys
Internal nameqcusbser
File version2. 0. 6. 7
CopyrightCopyright © 2001-2009

How the 24/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 imports99 / 100
IOCTL dispatch surface48 / 100
Known-vulnerable corpus0 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (19)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwSetValueKeymediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
IoDeleteSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign

IOCTL dispatch codes (16)

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
0x002215FFhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #1407
0x0022541FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #1287
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00800E84mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #929
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00808949mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #594
0x0080B841mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3600
0x00800045mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #17
0x00808B48mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #722
0x00220BE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #762
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00800065mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #25
0x003405E4mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #377

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x1A8280x1A8806.36CODE, EXEC, READ
.rdata0x0BD40x0C005.19IDATA, READ
.data0x04B40x05000.33IDATA, READ, WRITE
.pdata0x08A00x09004.85IDATA, READ
INIT0x0ACC0x0B005.02CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x06480x06803.33IDATA, READ, DISCARD
.reloc0x00B40x01001.08IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (9)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
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

SignerSqa.com(Test)
IssuerSqa.com(Test)
Serial77BC9236D94E9D89459641183A12768C
Valid from2010-03-08 04:59 UTC
Valid until2039-12-31 23:59 UTC
Signature validityVerified

Symbolic execution

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

Frequently asked questions about HtcVComV64.sys

Is HtcVComV64.sys safe?

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

What is the risk score of HtcVComV64.sys?

HtcVComV64.sys has a DriverShield composite risk score of 24/100, placing it in the clean verdict band. SHA256: 4cf12851a5a45917c3a9139b19d79434f2038611b617f83a714506cc7a1a6c61.

What is HtcVComV64.sys?

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

Related: Other drivers signed by Sqa.com(Test) · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact