WinCapture.sys - Clean (3/100) - DriverShield Analysis

Analysis of WinCapture.sys: clean verdict, risk score 3/100. 0 YARA matches. SHA256 7ada4bbea393cdd7. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

WinCapture.sys - Analysis Report

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

Verdict	Clean (3/100)
YARA matches	0
File size	4608 bytes
Analyzed	2026-07-18
SHA256	7ada4bbea393cdd7dc6f38cc3eda24e7ce08b6277d9c838cd41a4530e12c53df
SHA1	fd862c8048ffd3142128d92c27eeb58cf4e4173e
MD5	5f3161d4fcf438c0e77de0f88553b5fb

How the 3/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	3 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	50 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

IOCTL dispatch codes (1)

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
0x0022BAFF	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #3775

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	0x03F0	0x0400	5.66	CODE, EXEC, READ
.rdata	0x0070	0x0200	1.2	IDATA, READ
.pdata	0x0024	0x0200	0.28	IDATA, READ
.xdata	0x0014	0x0200	0.2	IDATA, READ
.bss	0x14040	0x0000	0	READ, WRITE
.edata	0x006F	0x0200	1.32	IDATA, READ
.idata	0x0018	0x0200	0	IDATA, READ, WRITE

Exploit mitigations

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

No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
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.
Unsigned - The driver is not digitally signed. It requires test signing mode or a bootloader exploit to load on 64-bit Windows.

MITRE ATT&CK techniques (3)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1543.003	Windows Service	Persistence
T1553.006	Code Signing Policy Modification	Defense Evasion
T1652	Device Driver Discovery	Discovery

Symbolic execution

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

Frequently asked questions about WinCapture.sys

Is WinCapture.sys safe?

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

What is the risk score of WinCapture.sys?

WinCapture.sys has a DriverShield composite risk score of 3/100, placing it in the clean verdict band. SHA256: 7ada4bbea393cdd7dc6f38cc3eda24e7ce08b6277d9c838cd41a4530e12c53df.

What is WinCapture.sys?

WinCapture.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators.