vms3cap.sys - Clean (5/100) - DriverShield Analysis

Analysis of vms3cap.sys: clean verdict, risk score 5/100. 0 YARA matches. SHA256 54bb8636f27282b3. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

vms3cap.sys - Analysis Report

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

Verdict	Clean (5/100)
YARA matches	0
File size	18960 bytes
Code-signing signer	Microsoft Windows
Analyzed	2026-03-22
SHA256	54bb8636f27282b396d487b3fea8bd73f2f6fe6da4de8d718ee498f75a6a5dce
SHA1	2258114da90b1239dad98d211d2ff45e1f9d959e
MD5	5914cc0c1e99a3c1711bdb1e224526d1

Driver identity

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

File description	Microsoft S3 Emulated Device Cap Driver
Product	Microsoft® Windows® Operating System
Company	Microsoft Corporation
Original filename	vms3cap.sys
Internal name	vms3cap.sys
File version	10.0.19041.1 (WinBuild.160101.0800)
Copyright	© Microsoft Corporation. All rights reserved.

How the 5/100 score breaks down

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

Component	Sub-score
Multi-engine consensus	0 / 100
YARA signature matches	0 / 100
Dangerous kernel imports	0 / 100
IOCTL dispatch surface	9 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (1)

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

API	Risk	Why it matters
DbgPrintEx	low	Standard kernel API - generally benign

IOCTL dispatch codes (3)

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.

Code	Severity	Transfer	Description
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x00220B0D	medium	METHOD_IN_DIRECT	FILE_DEVICE_UNKNOWN Function #707
0x003403AC	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #235

PE sections

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

Section	Virtual size	Raw size	Entropy	Flags
.text	0x0555	0x0600	5.27	CODE, EXEC, READ
.rdata	0x0890	0x0A00	4.47	IDATA, READ
.data	0x0330	0x0200	0.58	IDATA, READ, WRITE
.pdata	0x009C	0x0200	1.32	IDATA, READ
.idata	0x0164	0x0200	2.67	IDATA, READ
PAGE	0x004C	0x0200	1.22	CODE, EXEC, READ
INIT	0x00A2	0x0200	2.45	CODE, EXEC, READ, DISCARD
GFIDS	0x0014	0x0200	0.19	IDATA, READ, DISCARD
.rsrc	0x0420	0x0600	2.49	IDATA, READ, DISCARD
.reloc	0x00B8	0x0200	1.43	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Not enforced
Mitigation score	85 / 100

CFG Enabled - Control Flow Guard is active - indirect calls are validated against a bitmap of valid targets at runtime.
ASLR Enabled - Address Space Layout Randomization is active - base address is randomized on each load.
DEP/NX Enabled - Data Execution Prevention is active - non-executable pages cannot be executed.
Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

MITRE ATT&CK techniques (3)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1071	Application Layer Protocol	Command and Control
T1543.003	Windows Service	Persistence
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Microsoft Windows
Signer organisation	Microsoft Corporation
Issuer	Microsoft Windows Production PCA 2011
Serial	330000023241FB59996DCC4DFF000000000232
Valid from	2019-05-02 21:24 UTC
Valid until	2020-05-02 21:24 UTC (expired)
Signature validity	Not verified

Certificate revision: 0x0200
Certificate type: PKCS#7
Chain: Microsoft Windows Production PCA 2011

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 vms3cap.sys

Is vms3cap.sys safe?

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

What is the risk score of vms3cap.sys?

vms3cap.sys has a DriverShield composite risk score of 5/100, placing it in the clean verdict band. SHA256: 54bb8636f27282b396d487b3fea8bd73f2f6fe6da4de8d718ee498f75a6a5dce.

What is vms3cap.sys?

vms3cap.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