RTCore64.sys - Malicious (88/100) - DriverShield Analysis

Analysis of RTCore64.sys: malicious verdict, risk score 88/100. 3 YARA matches, 0/76 multi-engine detections. SHA256 a4f44e267698d47f. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

RTCore64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver RTCore64.sys and assigned a verdict of Malicious with a composite risk score of 88/100, indicating malicious indicators (80-100 band).

VerdictMalicious (88/100)
YARA matches3
Multi-engine detections0 / 76
File size40688 bytes
Code-signing signerGlobalSign
Analyzed2026-04-06
SHA256a4f44e267698d47f6a905e96b356582b4ee9cf4049e8c792ffda1b7356e68d35
SHA1f64cfef367b660631e224527e0ba93be822b2760
MD5589fa10ae27e8e5de36bc2356e253b11

How the 88/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 matches100 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface18 / 100
Known-vulnerable corpus0 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference40 / 100

Kernel imports (22)

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

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
HalSetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
KeBugCheckExmediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
IofCompleteRequestlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign

IOCTL dispatch codes (6)

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
0x0080E9C0mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2672
0x0022B941mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3664
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x12380x14005.81CODE, EXEC, READ
.rdata0x06D00x08003.81IDATA, READ
.data0x0F700x04001.45IDATA, READ, WRITE
.pdata0x02100x04002.42IDATA, READ
PAGE0x1A470x1C006.03CODE, EXEC, READ
INIT0x06340x08004.34CODE, EXEC, READ, WRITE, DISCARD
.reloc0x00600x02000.32IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (3)

RuleSeverityDetects
VULN_RTCore64criticalMSI RTCore64.sys
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (15)

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
T1014RootkitDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerGlobalSign
Signer organisationGlobalSign
IssuerGlobalSign
Serial45E6BB038333C3856548E6FF4551
Valid from2014-12-10 00:00 UTC
Valid until2034-12-10 00:00 UTC
Signature validityVerified

Associated CVEs

Symbolic execution

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

Frequently asked questions about RTCore64.sys

Is RTCore64.sys safe?

Based on DriverShield static and dynamic analysis, RTCore64.sys is flagged as malicious and should be treated as dangerous. Its composite risk score is 88/100 (verdict: malicious). Always validate findings independently before acting.

What is the risk score of RTCore64.sys?

RTCore64.sys has a DriverShield composite risk score of 88/100, placing it in the malicious verdict band. SHA256: a4f44e267698d47f6a905e96b356582b4ee9cf4049e8c792ffda1b7356e68d35.

What is RTCore64.sys?

RTCore64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by GlobalSign.

Related: Other drivers signed by GlobalSign · CVE-2019-16098 · 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