ramdisk.sys - Suspicious (58/100) - DriverShield Analysis

Analysis of ramdisk.sys: suspicious verdict, risk score 58/100. 2 YARA matches. SHA256 d461798c6348c5d9. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

ramdisk.sys - Analysis Report

DriverShield analyzed the Windows kernel driver ramdisk.sys and assigned a verdict of Suspicious with a composite risk score of 58/100, indicating some risk signals warranting review (30-59 band).

Verdict	Suspicious (58/100)
YARA matches	2
File size	42296 bytes
Code-signing signer	Microsoft Windows
Analyzed	2026-03-22
SHA256	d461798c6348c5d96ea002e4a1ac588b87a1a9b01ad84ab1fa6d9c6393616892
SHA1	07de23355bcc3e9c0d64175d227ee33f586f3661
MD5	9d377a5872a0a7a33e258ffcbdb3f25f

Driver identity

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

File description	RAM Disk Driver
Product	Microsoft® Windows® Operating System
Company	Microsoft Corporation
Original filename	ramdisk.sys
Internal name	ramdisk.sys
File version	10.0.19041.1 (WinBuild.160101.0800)
Copyright	© Microsoft Corporation. All rights reserved.

How the 58/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	80 / 100
Dangerous kernel imports	100 / 100
IOCTL dispatch surface	12 / 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 (18)

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

API	Risk	Why it matters
MmMapLockedPagesSpecifyCache	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
MmUnmapIoSpace	medium	Moderate risk - system modification capability
ZwQueryValueKey	low	Standard kernel API - generally benign
ZwOpenKey	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign
ZwQueryInformationFile	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
PsGetCurrentProcess	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
KeInitializeEvent	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
KeSetEvent	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign

IOCTL dispatch codes (4)

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
0x00808589	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #354
0x0034037C	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #223

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	0x1569	0x1600	6.03	CODE, EXEC, READ
.rdata	0x0AD8	0x0C00	4.23	IDATA, READ
.data	0x00D8	0x0200	0.28	IDATA, READ, WRITE
.pdata	0x0270	0x0400	2.83	IDATA, READ
.idata	0x0AEE	0x0C00	4.28	IDATA, READ
PAGE	0x382F	0x3A00	6.17	CODE, EXEC, READ
INIT	0x0572	0x0600	5.34	CODE, EXEC, READ, DISCARD
GFIDS	0x003C	0x0200	0.53	IDATA, READ, DISCARD
.rsrc	0x03F0	0x0400	3.28	IDATA, READ, DISCARD
.reloc	0x040C	0x0600	3.9	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.

YARA rule matches (2)

Rule	Severity	Detects
BYOVD_MemRW	critical	Phys memory mapping + device creation
SUSP_PhysMem	high	Physical memory mapping

MITRE ATT&CK techniques (11)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1112	Modify Registry	Defense Evasion
T1211	Exploitation for Defense Evasion	Defense Evasion
T1543.003	Windows Service	Persistence
T1547.001	Registry Run Keys	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1569.002	Service Execution	Execution
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 ramdisk.sys

Is ramdisk.sys safe?

Based on DriverShield static and dynamic analysis, ramdisk.sys shows some suspicious signals and warrants manual review. Its composite risk score is 58/100 (verdict: suspicious). Always validate findings independently before acting.

What is the risk score of ramdisk.sys?

ramdisk.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: d461798c6348c5d96ea002e4a1ac588b87a1a9b01ad84ab1fa6d9c6393616892.

What is ramdisk.sys?

ramdisk.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 · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas

---

DriverShield © 2025-2026 · Terms · Privacy · Contact