beep.sys - Clean (8/100) - DriverShield Analysis

Analysis of beep.sys: clean verdict, risk score 8/100. 0 YARA matches. SHA256 121af03bbe6ecc16. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

beep.sys - Analysis Report

DriverShield analyzed the Windows kernel driver beep.sys and assigned a verdict of Clean with a composite risk score of 8/100, indicating no notable risk signals (0-29 band).

Verdict	Clean (8/100)
YARA matches	0
File size	10240 bytes
Analyzed	2026-03-22
SHA256	121af03bbe6ecc1622c2540805a30ae9555eb5d5fe25b55939c045ece7fc37eb
SHA1	9c6c145c0d88919dc7a8573f036ef2c860f8a8f3
MD5	4280b427b81eb8c265f3206e2298761e

Driver identity

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

File description	BEEP Driver
Product	Microsoft® Windows® Operating System
Company	Microsoft Corporation
Original filename	beep.sys
Internal name	beep.sys
File version	10.0.19041.1 (WinBuild.160101.0800)
Copyright	© Microsoft Corporation. All rights reserved.

How the 8/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	0 / 100
Dangerous kernel imports	24 / 100
IOCTL dispatch surface	6 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	50 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (5)

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

API	Risk	Why it matters
RtlInitUnicodeString	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
KeInitializeEvent	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign

IOCTL dispatch codes (2)

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
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x0034036C	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #219

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	0x0965	0x0A00	5.35	CODE, EXEC, READ
.rdata	0x04D8	0x0600	3.4	IDATA, READ
.data	0x0090	0x0200	0.28	IDATA, READ, WRITE
.pdata	0x0150	0x0200	2.64	IDATA, READ
.idata	0x0410	0x0600	3.22	IDATA, READ
INIT	0x0072	0x0200	1.67	CODE, EXEC, READ, DISCARD
GFIDS	0x0040	0x0200	0.56	IDATA, READ, DISCARD
.rsrc	0x03E0	0x0400	3.22	IDATA, READ, DISCARD
.reloc	0x0108	0x0200	2.61	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Not enforced
Mitigation score	80 / 100

CFG Enabled - Control Flow Guard is active - indirect calls are validated against a bitmap of valid targets at runtime.
ASLR Enabled - Address Space Layout Randomization is active - base address is randomized on each load.
DEP/NX Enabled - Data Execution Prevention is active - non-executable pages cannot be executed.
Unsigned - The driver is not digitally signed. It requires test signing mode or a bootloader exploit to load on 64-bit Windows.

MITRE ATT&CK techniques (4)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1543.003	Windows Service	Persistence
T1553.006	Code Signing Policy Modification	Defense Evasion
T1569.002	Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Symbolic execution

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

Frequently asked questions about beep.sys

Is beep.sys safe?

Based on DriverShield static and dynamic analysis, beep.sys is assessed as clean, with no notable risk signals. Its composite risk score is 8/100 (verdict: clean). Always validate findings independently before acting.

What is the risk score of beep.sys?

beep.sys has a DriverShield composite risk score of 8/100, placing it in the clean verdict band. SHA256: 121af03bbe6ecc1622c2540805a30ae9555eb5d5fe25b55939c045ece7fc37eb.

What is beep.sys?

beep.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators.