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

Analysis of Ld9BoxSup.sys: suspicious verdict, risk score 58/100. 1 YARA match, 0/76 multi-engine detections. SHA256 980641ff6df79cc5. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

Ld9BoxSup.sys - Analysis Report

DriverShield analyzed the Windows kernel driver Ld9BoxSup.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	1
Multi-engine detections	0 / 76
File size	354200 bytes
Code-signing signer	Microsoft Windows Hardware Compatibility Publisher
Analyzed	2026-04-14
SHA256	980641ff6df79cc598935e8888a8bcb136b94546781953c05f53fc3d068acb13
SHA1	dc8222ccbd900d839917259d79c329be94ccd525
MD5	d3ffe15c357ffa6080139570adc143c1

Driver identity

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

File description	VirtualBox Support Driver
Product	Oracle VM VirtualBox
Company	Oracle Corporation
Original filename	VBoxSup.sys
Internal name	VBoxSup
File version	6.1.36.152435
Copyright	Copyright (C) 2009-2022 Oracle Corporation

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	30 / 100
Dangerous kernel imports	100 / 100
IOCTL dispatch surface	100 / 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 (27)

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

API	Risk	Why it matters
MmMapLockedPagesSpecifyCache	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPages	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpace	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddress	high	Potentially dangerous - could be used for privilege escalation or security bypass
ZwSetSystemInformation	high	Potentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddress	high	Potentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemorySpecifyCache	high	Potentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemory	high	Potentially dangerous - could be used for privilege escalation or security bypass
ZwQuerySystemInformation	medium	Moderate risk - system modification capability
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
MmUnmapIoSpace	medium	Moderate risk - system modification capability
IoBuildDeviceIoControlRequest	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
ExFreePool	low	Standard kernel API - generally benign
ExAllocatePool	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign
KeInitializeEvent	low	Standard kernel API - generally benign
ProbeForRead	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
KeSetEvent	low	Standard kernel API - generally benign
KeDelayExecutionThread	low	Standard kernel API - generally benign
DbgPrint	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
ProbeForWrite	low	Standard 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.

Code	Severity	Transfer	Description
0x0080BD8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3938
0x0022804B	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #18
0x0080878B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #482
0x00809F8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #2018
0x00808987	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #609
0x0080A98B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #2658
0x0080968B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #1442
0x0080A38B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #2274
0x0080998B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #1634
0x0080BA8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3746
0x0022805F	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #23
0x0080B08B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3106
0x0080850F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #323
0x00228057	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #21
0x00228053	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #20
0x008083C7	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #241
0x0080880F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #515
0x00801C8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #1826
0x0080048B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #290
0x00801483	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #1312
0x0080B8C3	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3632
0x0080858B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #354
0x00347263	high	METHOD_NEITHER	FILE_DEVICE_DISK Function #3224
0x00805A4D	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #1683

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.

Section	Virtual size	Raw size	Entropy	Flags
.text	0x33EF0	0x34000	6.43	CODE, EXEC, READ
.rdata	0x10FB0	0x11000	5.91	IDATA, READ
.data	0x20D40	0x5200	3.54	IDATA, READ, WRITE
.pdata	0x3B04	0x3C00	5.52	IDATA, READ
.edata	0x3E04	0x4000	5.87	IDATA, READ
INIT	0x085A	0x0A00	4.54	CODE, EXEC, READ, WRITE, DISCARD
.rsrc	0x03F8	0x0400	3.4	IDATA, READ, DISCARD
.reloc	0x1044	0x1200	3.7	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Not enabled
DEP	Not enabled
Integrity check	Not enforced
Mitigation score	5 / 100

• No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
• No ASLR - ASLR is disabled. The driver loads at a predictable address, enabling reliable exploitation of memory corruption vulnerabilities.
• No DEP - DEP is disabled. Data pages are executable, allowing shellcode execution from stack/heap buffers.
• Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

YARA rule matches (1)

Rule	Severity	Detects
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	OS Credential Dumping	Credential Access
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1006	Direct Volume Access	Defense Evasion
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1211	Exploitation for Defense Evasion	Defense Evasion
T1543.003	Windows Service	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 Hardware Compatibility Publisher
Signer organisation	Microsoft Corporation
Issuer	Microsoft Windows Third Party Component CA 2012
Serial	33000000DC341A520FBBCF3D8C0000000000DC
Valid from	2022-03-10 19:58 UTC
Valid until	2023-03-08 19:58 UTC (expired)
Signature validity	Not verified

• Certificate revision: 0x0200
• Certificate type: PKCS#7
• Chain: Microsoft Windows Third Party Component CA 2012

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

Is Ld9BoxSup.sys safe?

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

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

What is Ld9BoxSup.sys?

Ld9BoxSup.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