fancyrd.sys - Vulnerable (72/100) - DriverShield Analysis

Analysis of fancyrd.sys: vulnerable verdict, risk score 72/100. 2 YARA matches, 0/76 multi-engine detections. SHA256 495a10b0ee378a2d. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

fancyrd.sys - Analysis Report

DriverShield analyzed the Windows kernel driver fancyrd.sys and assigned a verdict of Vulnerable with a composite risk score of 72/100, indicating a known or likely vulnerability surface (60-79 band).

VerdictVulnerable (72/100)
YARA matches2
Multi-engine detections0 / 76
File size202344 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-08-18
SHA256495a10b0ee378a2d33fec80c6762fcc4e10f2dfeff6fc8abdb8fbe33a447959f
SHA1dc66b148e5905cd36505e45772819615b780f9cd
MD53f1158c09ca9d103123f04ebb1ed5008

Driver identity

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

File descriptionPrimo Ramdisk Driver
ProductPrimo Ramdisk
CompanyRomex Software
Original filenamefancyrd.sys
Internal namefancyrd.sys
File version6.6.0
Copyright(C) Romex Software. All rights reserved.

How the 72/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 matches80 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface100 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (32)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ZwWriteFilemediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwDeleteFilemediumModerate risk - system modification capability
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 32 resolved.

IOCTL dispatch codes (40)

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
0x0080968BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1442
0x00808B8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #738
0x00808F8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #994
0x00340063highMETHOD_NEITHERFILE_DEVICE_DISK Function #24
0x00227417highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3333
0x00220117highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #69
0x0080BAC7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3761
0x0080B703highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3520
0x00809F03highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1984
0x0080A703highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2496
0x0080878BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #482
0x00809703highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1472
0x008087C7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #497
0x003445C7highMETHOD_NEITHERFILE_DEVICE_DISK Function #369
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x008083C6mediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #241
0x00808B8DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #739
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x00802824mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2569
0x00228BE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #762

Showing 24 of 40 extracted control codes.

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x15AD50x15C006.43CODE, EXEC, READ
EXTRA0x22210x24006.11CODE, EXEC, READ
CPATA0x01910x02000.99CODE, EXEC, READ
.rdata0x71B00x72005.77IDATA, READ
.data0x05000x04004.1IDATA, READ, WRITE
.pdata0x15E40x16005.25IDATA, READ
PAGE0xA3FA0xA4006.41CODE, EXEC, READ
INIT0x2A5E0x2C006.2CODE, EXEC, READ, DISCARD
.rsrc0x08900x0A003.1IDATA, READ, DISCARD
.reloc0x013C0x02003.63IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score85 / 100

YARA rule matches (2)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (12)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003OS Credential DumpingCredential Access
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1006Direct Volume AccessDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2014
Serial330000004DE597A775E3157F7B00000000004D
Valid from2021-09-09 19:15 UTC
Valid until2022-09-01 19:15 UTC (expired)
Signature validityNot verified

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

Is fancyrd.sys safe?

Based on DriverShield static and dynamic analysis, fancyrd.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 72/100 (verdict: vulnerable). Always validate findings independently before acting.

What is the risk score of fancyrd.sys?

fancyrd.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 495a10b0ee378a2d33fec80c6762fcc4e10f2dfeff6fc8abdb8fbe33a447959f.

What is fancyrd.sys?

fancyrd.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 Hardware Compatibility Publisher.

Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · 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