f853abe0dc162601e66e4a346faed8... - Vulnerable (72/100) - DriverShield Analysis

Analysis of f853abe0dc162601e66e4a346faed854.sys: vulnerable verdict, risk score 72/100. 3 YARA matches, 3/76 multi-engine detections. SHA256 1e0eb0811a7cf1bd. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

f853abe0dc162601e66e4a346faed854.sys - Analysis Report

DriverShield analyzed the Windows kernel driver f853abe0dc162601e66e4a346faed854.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 matches3
Multi-engine detections3 / 76
File size22312 bytes
Code-signing signerVeriSign Time Stamping Services Signer - G2
Analyzed2026-03-24
SHA2561e0eb0811a7cf1bdaf29d3d2cab373ca51eb8d8b58889ab7728e2d3aed244abe
SHA135b28b15835aa0775b57f460d8a03e53dc1fb30f
MD5f853abe0dc162601e66e4a346faed854

Driver identity

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

File descriptionRwDrv Driver
ProductRwDrv Driver
CompanyRW-Everything
Original filenameRwDrv.sys
Internal nameRwDrv.sys
File version1.00.00.0000 built by: WinDDK
CopyrightCopyright (C) 2011 RW-Everything

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 matches85 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface27 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (16)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemorySpecifyCachehighPotentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpacemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
IoCreateDevicelowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign

IOCTL dispatch codes (9)

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
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00222858mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2582
0x00222830mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2572
0x00222834mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2573
0x0022285CmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2583
0x00222880mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2592
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00808789mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #482
0x0034030CmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #195

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x1D880x1E006.27CODE, EXEC, READ
.rdata0x02DC0x04003.44IDATA, READ
.data0x01300x02000.3IDATA, READ, WRITE
.pdata0x01080x02002.23IDATA, READ
INIT0x06D80x08004.91CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03700x04002.91IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLRNot enabled
DEPNot enabled
Integrity checkNot enforced
Mitigation score5 / 100

YARA rule matches (3)

RuleSeverityDetects
PUA_VULN_Driver_Rweverything_Rwdrvsys_Rwdrvdriver_45BAmediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - RwDrv.sys
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (14)

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
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerVeriSign Time Stamping Services Signer - G2
Signer organisationVeriSign, Inc.
IssuerVeriSign Time Stamping Services CA
Serial3825D7FAF861AF9EF490E726B5D65AD5
Valid from2007-06-15 00:00 UTC
Valid until2012-06-14 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Corpus match: this hash is present in the known-vulnerable driver corpus DriverShield cross-references during analysis, which is why the score carries a full weighting on that component.

Frequently asked questions about f853abe0dc162601e66e4a346faed854.sys

Is f853abe0dc162601e66e4a346faed854.sys safe?

Based on DriverShield static and dynamic analysis, f853abe0dc162601e66e4a346faed854.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 f853abe0dc162601e66e4a346faed854.sys?

f853abe0dc162601e66e4a346faed854.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 1e0eb0811a7cf1bdaf29d3d2cab373ca51eb8d8b58889ab7728e2d3aed244abe.

What is f853abe0dc162601e66e4a346faed854.sys?

f853abe0dc162601e66e4a346faed854.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by VeriSign Time Stamping Services Signer - G2.

Related: Other drivers signed by VeriSign Time Stamping Services Signer - G2 · 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