RegGuard.sys - Clean (19/100) - DriverShield Analysis

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

RegGuard.sys - Analysis Report

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

Verdict	Clean (19/100)
YARA matches	0
File size	13312 bytes
Analyzed	2026-09-02
SHA256	3f1e3e3df97b4befadd51f1d4a447b34801a67e19b9023aef8b11c6aacbcc919
SHA1	2f0e2a2a9ccc63bdd4954b876b6483fa194263b2
MD5	a14cf1cf76b9d1788ce79dfa089d1a18

Driver identity

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

File description	NoVirusThanks Registry Guard Driver
Product	NoVirusThanks Registry Guard Driver
Company	NoVirusThanks Company Srl
Original filename	RegGuard.sys
Internal name	RegGuard.sys
File version	1.0.0.0 built by: WinDDK
Copyright	NoVirusThanks Company Srl

How the 19/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	84 / 100
IOCTL dispatch surface	9 / 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

Kernel imports (8)

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

API	Risk	Why it matters
ZwMapViewOfSection	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
KeBugCheckEx	medium	Moderate risk - system modification capability
ZwWriteFile	medium	Moderate risk - system modification capability
CmRegisterCallbackEx	medium	Moderate risk - system modification capability
ZwOpenFile	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	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
0x00802484	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2337
0x00340368	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #218

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	0x1D0E	0x1E00	6.04	CODE, EXEC, READ
.rdata	0x0264	0x0400	2.58	IDATA, READ
.data	0x0254	0x0200	0.49	IDATA, READ, WRITE
.pdata	0x00C0	0x0200	1.67	IDATA, READ
INIT	0x038A	0x0400	4.75	CODE, EXEC, READ, WRITE, DISCARD
.rsrc	0x03C8	0x0400	3.13	IDATA, READ, DISCARD
.reloc	0x0018	0x0200	0.12	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Not enabled
DEP	Not enabled
Integrity check	Not enforced
Mitigation score	0 / 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.
No ASLR - ASLR is disabled. The driver loads at a predictable address, enabling reliable exploitation of memory corruption vulnerabilities.
No DEP - DEP is disabled. Data pages are executable, allowing shellcode execution from stack/heap buffers.
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 (13)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1014	Rootkit	Defense Evasion
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1211	Exploitation for Defense Evasion	Defense Evasion
T1543.003	Windows Service	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1553.006	Code Signing Policy Modification	Defense Evasion
T1562.006	Indicator Blocking	Defense Evasion
T1564.001	Hidden Files and Directories	Defense Evasion
T1569.002	Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Symbolic execution

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

Frequently asked questions about RegGuard.sys

Is RegGuard.sys safe?

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

What is the risk score of RegGuard.sys?

RegGuard.sys has a DriverShield composite risk score of 19/100, placing it in the clean verdict band. SHA256: 3f1e3e3df97b4befadd51f1d4a447b34801a67e19b9023aef8b11c6aacbcc919.

What is RegGuard.sys?

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