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

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

xhunter2.sys - Analysis Report

DriverShield analyzed the Windows kernel driver xhunter2.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 matches1
Multi-engine detections0 / 75
File size243384 bytes
Code-signing signerDigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Analyzed2026-09-28
SHA2562a08d36367d696f9bca43f75c0c561f13914fc59fccab9c02e442405a8973097
SHA137070b0221854590de56579c35a844513eca856e
MD53188e7001cefe159ffc8b426ebf178bb

Driver identity

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

File descriptionWellbia.com System Guard
ProductWellbia.com System Guard
CompanyWellbia.com Co., Ltd.
Original filenamexhunter1.sys
Internal namexhunter1.sys
File version2026.7.18.294
CopyrightCopyright (c) 2006-2023 Wellbia.com Co., Ltd.

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 matches5 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface100 / 100
Known-vulnerable corpus0 / 100
Code-signing state0 / 100
Packing and entropy80 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (34)

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

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsSetCreateProcessNotifyRoutineExhighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutinehighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially 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
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
ObOpenObjectByPointermediumModerate risk - system modification capability
CmRegisterCallbackExmediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwCreateFilelowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ProbeForReadlowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 34 resolved.

IOCTL dispatch codes (39)

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
0x0022B8DBhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3638
0x00224043highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #16
0x00808D0FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #835
0x0034840FhighMETHOD_NEITHERFILE_DEVICE_DISK Function #259
0x0034850FhighMETHOD_NEITHERFILE_DEVICE_DISK Function #323
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x9C404E38mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #910
0x00809389mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1250
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080B841mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3600
0x0080BB01mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3776
0x0022B80CmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3587
0x00228556mediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #341
0x0034EB15mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2757
0x0034002DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #11
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13
0x0034C100mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #64
0x0034C0F8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #62
0x0034C120mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #72
0x00341500mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #1344
0x00226728mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2506
0x002265C8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2418

Showing 24 of 39 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
.text0x150880x152007.07CODE, EXEC, READ
.rdata0xD2DC0xD4004.06IDATA, READ
.data0x44F80x38005.16IDATA, READ, WRITE
.pdata0x10500x12007.64IDATA, READ
INIT0x0FB20x10005.39CODE, EXEC, READ
. 3P0xD7680xD8006.13CODE, EXEC, READ
.reloc0x00740x02001.55IDATA, READ, DISCARD
.rsrc0x043C0x06002.78IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score75 / 100

YARA rule matches (1)

RuleSeverityDetects
SUSP_CallbacksmediumKernel callback registration

MITRE ATT&CK techniques (17)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1014RootkitDefense Evasion
T1055.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair Defenses: Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerDigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Signer organisationDigiCert, Inc.
IssuerDigiCert Trusted Root G4
Serial8AD40B260D29C4C9F5ECDA9BD93AED9
Valid from2021-04-29 00:00 UTC
Valid until2036-04-28 23:59 UTC
Signature validityVerified

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

Is xhunter2.sys safe?

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

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

What is xhunter2.sys?

xhunter2.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1.

Related: Other drivers signed by DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1 · 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