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

Analysis of l1malwarebits.sys: suspicious verdict, risk score 58/100. 2 YARA matches, 0/76 multi-engine detections. SHA256 d6d219628ab3acdc. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

l1malwarebits.sys - Analysis Report

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

VerdictSuspicious (58/100)
YARA matches2
Multi-engine detections0 / 76
File size30776 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-04-21
SHA256d6d219628ab3acdc799b1b631d378742a4b266d6f55b12e568e4054091b08be6
SHA136c520b1d814ee89bd9161f6b31953fa2ae7850b
MD5b3ce4e620e0e7c45f84000c5eac2a8e9

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.

ComponentSub-score
Multi-engine consensus0 / 100
YARA signature matches80 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface36 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (17)

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

APIRiskWhy it matters
MmCopyVirtualMemorycriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
IoCreateDevicelowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign

IOCTL dispatch codes (12)

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
0x0080830FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #195
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0022B7E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3578
0x00221844mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1553
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00348B05mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #705
0x00228715mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #453
0x00225715mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1477
0x00222F15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3013
0x00220F05mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #961
0x00220F15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #965
0x00220020mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #8

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x2C5D0x2E006.11CODE, EXEC, READ
.rdata0x0C7C0x0E004.3IDATA, READ
.data0x03780x02000.81IDATA, READ, WRITE
.pdata0x02880x04002.89IDATA, READ
INIT0x064A0x08004.2CODE, EXEC, READ, DISCARD
.reloc0x00380x02000.73IDATA, 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 (13)

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.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair Defenses: Disable/Modify ToolsDefense 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
Serial3300000062F45CF99E58A96A89000000000062
Valid from2023-04-06 19:16 UTC
Valid until2024-04-03 19:16 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 l1malwarebits.sys

Is l1malwarebits.sys safe?

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

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

What is l1malwarebits.sys?

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