rt640x64.sys - Suspicious (35/100) - DriverShield Analysis

Analysis of rt640x64.sys: suspicious verdict, risk score 35/100. 1 YARA match, 0/75 multi-engine detections. SHA256 3af292bcbd169fd3. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

rt640x64.sys - Analysis Report

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

VerdictSuspicious (35/100)
YARA matches1
Multi-engine detections0 / 75
File size1331144 bytes
Code-signing signerDigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Analyzed2026-05-03
SHA2563af292bcbd169fd3bf1c3cb90d5b7f4649dd2625afc7ed285df249926367186a
SHA176cdd4860412da4ea62d2745c84a29a28dffadcd
MD54b73b8347f14a3a980e8f5edb1e8ebfe

Driver identity

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

File descriptionRealtek 8125/8126/8136/8168/8169 NDIS 6.40 64-bit Driver
ProductRealtek 8125/8126/8136/8168/8169 PCI/PCIe Adapters
CompanyRealtek
Original filenamert640x64.sys
Internal namert640x64.sys
File version10.071.0312.2024
CopyrightCopyright (C) 2024 Realtek Semiconductor Corporation. All Rights Reserved.

How the 35/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 matches30 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface100 / 100
Known-vulnerable corpus0 / 100
Code-signing state0 / 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 rt640x64.sys, ranked by exploitation relevance.

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
IofCompleteRequestlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign

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
0x00807FA3highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #4072
0x00807FABhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #4074
0x00802093highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2084
0x00807FBBhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #4078
0x008020BBhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2094
0x008039A3highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3688
0x00803C83highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3872
0x00803D83highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3936
0x00803883highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3616
0x0080DFB3highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2028
0x00809CB3highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1836
0x0080D0B7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1069
0x0080C7FFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #511
0x00807087highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3105
0x0080BDBFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3951
0x0080A3B7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2285
0x0080840FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #259
0x0080F0B7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3117
0x0080BDAFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3947
0x0080A9A7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2665
0x0080F0BFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3119
0x008090A7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1065
0x00801CA7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1833
0x0080A9BBhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2670

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
.text0x11DE840x11E0006.22CODE, EXEC, READ
.rdata0x1744C0x176005.61IDATA, READ
.data0x1CC00x1A002.52IDATA, READ, WRITE
.pdata0x34A40x36005.78IDATA, READ
PAGE0x072C0x08005.68CODE, EXEC, READ
INIT0x16320x18005.52CODE, EXEC, READ, DISCARD
.rsrc0x06800x08002.79IDATA, READ, DISCARD
.reloc0x2C6C0x2E006.01IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (1)

RuleSeverityDetects
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (11)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
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
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerDigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Signer organisationDigiCert, Inc.
IssuerDigiCert Trusted Root G4
Serial8AD40B260D29C4C9F5ECDA9BD93AED9
Valid from2021-04-29 00:00 UTC
Valid until2036-04-28 23:59 UTC
Signature validityVerified

Symbolic execution

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

Frequently asked questions about rt640x64.sys

Is rt640x64.sys safe?

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

What is the risk score of rt640x64.sys?

rt640x64.sys has a DriverShield composite risk score of 35/100, placing it in the suspicious verdict band. SHA256: 3af292bcbd169fd3bf1c3cb90d5b7f4649dd2625afc7ed285df249926367186a.

What is rt640x64.sys?

rt640x64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1.

Related: Other drivers signed by DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1 · 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