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

Analysis of mhyprot2.sys: malicious verdict, risk score 88/100. 3 YARA matches, 4/74 multi-engine detections. SHA256 46cf46e1073b7c99. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

mhyprot2.sys - Analysis Report

DriverShield analyzed the Windows kernel driver mhyprot2.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 detections4 / 74
File size1334824 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-09-06
SHA25646cf46e1073b7c99142964b7c4bef1e5285fabcf2c6dbe5be99000a393d9f474
SHA1296757d5663290f172e99e60b9059f989cba4c4e
MD5d717f8de642b65f029829c34fbd13a45

Driver identity

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

File description"ProductName
Product&ProductVersion
Company*FileDescription
Original filenameD
Internal name*OriginalFilename
Copyright©COGNOSPHERE

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 surface93 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy80 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (30)

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

APIRiskWhy it matters
MmCopyVirtualMemorycriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagescriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutinehighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutineExhighPotentially dangerous - could be used for privilege escalation or security bypass
ObRegisterCallbackshighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
ObOpenObjectByPointermediumModerate risk - system modification capability
PsSetCreateThreadNotifyRoutinemediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
NtQuerySystemInformationmediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ZwWriteFilemediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
IofCompleteRequestlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 30 resolved.

IOCTL dispatch codes (31)

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
0x9C400693highMETHOD_NEITHERCUSTOM_LENOVO Function #420
0x9C400753highMETHOD_NEITHERCUSTOM_LENOVO Function #468
0x0080F87FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3615
0x9C40FEF7highMETHOD_NEITHERCUSTOM_LENOVO Function #4029
0xC35041FFhighMETHOD_NEITHERCUSTOM_MSI Function #127
0xC35041C7highMETHOD_NEITHERCUSTOM_MSI Function #113
0xC35041C3highMETHOD_NEITHERCUSTOM_MSI Function #112
0xC35041E7highMETHOD_NEITHERCUSTOM_MSI Function #121
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080928DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1187
0x0080808DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #35
0x002273E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3322
0x002263E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2298
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x9C400DDEmediumMETHOD_OUT_DIRECTCUSTOM_LENOVO Function #887
0x82739F74mediumMETHOD_BUFFEREDCUSTOM_VIRAGT Function #2013
0xC350FF0DmediumMETHOD_IN_DIRECTCUSTOM_MSI Function #4035
0xC350797AmediumMETHOD_OUT_DIRECTCUSTOM_MSI Function #3678
0xC3504100mediumMETHOD_BUFFEREDCUSTOM_MSI Function #64
0xC35041E0mediumMETHOD_BUFFEREDCUSTOM_MSI Function #120
0xC35041C0mediumMETHOD_BUFFEREDCUSTOM_MSI Function #112
0xC35041C1mediumMETHOD_IN_DIRECTCUSTOM_MSI Function #112
0xC35041C2mediumMETHOD_OUT_DIRECTCUSTOM_MSI Function #112

Showing 24 of 31 extracted control codes.

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x6B300x6C006.13CODE, EXEC, READ
.rdata0x15240x16004.62IDATA, READ
.data0x15F80x02000.81IDATA, READ, WRITE
.pdata0x06600x08006.84IDATA, READ
PAGE0x0B0A0x0C005.34CODE, EXEC, READ
INIT0x0EAE0x10005.09CODE, EXEC, READ
.upx00x1382340x1384007.11CODE, IDATA, EXEC, READ
.reloc0x00D80x02001.97IDATA, READ, DISCARD
.rsrc0x02600x04001.99IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (3)

RuleSeverityDetects
BYOVD_ProcKillcriticalProcess termination EDR killer
SUSP_CallbacksmediumKernel callback registration
MAL_EDRKillercriticalGeneric EDR killer pattern

MITRE ATT&CK techniques (16)

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.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.001Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense 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
Serial330000004DE597A775E3157F7B00000000004D
Valid from2021-09-09 19:15 UTC
Valid until2022-09-01 19:15 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Corpus match: this hash is present in the known-vulnerable driver corpus DriverShield cross-references during analysis, which is why the score carries a full weighting on that component.

Frequently asked questions about mhyprot2.sys

Is mhyprot2.sys safe?

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

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

What is mhyprot2.sys?

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