mausbip.sys - Clean (18/100) - DriverShield Analysis

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

mausbip.sys - Analysis Report

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

VerdictClean (18/100)
YARA matches0
File size64016 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-03-22
SHA256aeadb11e2be2eeb4bb5e4e13adda4633475022312aee777cfe7feb27c490b54c
SHA1695fee073d94c0db8dbb55ab442cdf3b446199ad
MD56c6c1efc46a62091224333e1e9304fbc

Driver identity

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

File descriptionMA-USB IP Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenamemauship.sys
Internal namemausbip.sys
File version10.0.19041.1 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 18/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 matches0 / 100
Dangerous kernel imports60 / 100
IOCTL dispatch surface27 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (8)

Kernel-mode APIs resolved from the Import Address Table of mausbip.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
ExAllocatePoolWithTaglowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign

IOCTL dispatch codes (9)

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
0x00805B0DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1731
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080AB05mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2753
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00343FE8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #4090
0x0022011DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #71
0x0022341CmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3335
0x00340380mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #224

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x8C290x8E006.09CODE, EXEC, READ
.rdata0x18780x1A005.41IDATA, READ
.data0x05380x02001.69IDATA, READ, WRITE
.pdata0x04E00x06003.79IDATA, READ
.idata0x07EE0x08004.41IDATA, READ
PAGE0x0D6D0x0E005.94CODE, EXEC, READ
INIT0x00360x02000.87CODE, EXEC, READ, DISCARD
GFIDS0x00540x02000.77IDATA, READ, DISCARD
.rsrc0x03F00x04003.3IDATA, READ, DISCARD
.reloc0x05A00x06005.59IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (8)

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
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial330000023241FB59996DCC4DFF000000000232
Valid from2019-05-02 21:24 UTC
Valid until2020-05-02 21:24 UTC (expired)
Signature validityNot verified

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

Is mausbip.sys safe?

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

What is the risk score of mausbip.sys?

mausbip.sys has a DriverShield composite risk score of 18/100, placing it in the clean verdict band. SHA256: aeadb11e2be2eeb4bb5e4e13adda4633475022312aee777cfe7feb27c490b54c.

What is mausbip.sys?

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

Related: Other drivers signed by Microsoft Windows · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact