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

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

xhunter1.sys - Analysis Report

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

Verdict	Suspicious (58/100)
YARA matches	2
Multi-engine detections	5 / 75
File size	48368 bytes
Code-signing signer	Symantec Time Stamping Services CA - G2
Analyzed	2026-09-06
SHA256	e727d0753d2cd0b2f6eeba4cea53aa10b3ff3ed2afeb78f545fcf6d840f85c3e
SHA1	852049ecfd6a42370f2d6ed0d5e67e52c8d88211
MD5	c61c16de83acabd35ee18e410c1c37c1

Driver identity

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

File description	XIGNCODE3 System Guard
Product	XIGNCODE3
Company	Wellbia.com Co., Ltd.
Original filename	xhunter1.sys
Internal name	xhunter1.sys
File version	10.0.10011.16384
Copyright	Copyright (c) 2006-2013 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.

Component	Sub-score
Multi-engine consensus	0 / 100
YARA signature matches	10 / 100
Dangerous kernel imports	100 / 100
IOCTL dispatch surface	27 / 100
Known-vulnerable corpus	100 / 100
Code-signing state	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (28)

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

API	Risk	Why it matters
MmMapLockedPagesSpecifyCache	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ObRegisterCallbacks	high	Potentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutine	high	Potentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessId	high	Potentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutineEx	high	Potentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddress	high	Potentially dangerous - could be used for privilege escalation or security bypass
ZwQuerySystemInformation	medium	Moderate risk - system modification capability
ObOpenObjectByPointer	medium	Moderate risk - system modification capability
KeBugCheckEx	medium	Moderate risk - system modification capability
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
IoCreateSymbolicLink	low	Standard kernel API - generally benign
KeDelayExecutionThread	low	Standard kernel API - generally benign
ProbeForWrite	low	Standard kernel API - generally benign
ZwCreateFile	low	Standard kernel API - generally benign
ZwReadFile	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign
ZwQueryInformationFile	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
ProbeForRead	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
KeSetEvent	low	Standard kernel API - generally benign
ExAllocatePool	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
ZwOpenFile	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard 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.

Code	Severity	Transfer	Description
0x00801F0F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #1987
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x0080249C	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2343
0x00802484	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2337
0x0022B941	medium	METHOD_IN_DIRECT	FILE_DEVICE_UNKNOWN Function #3664
0x00340340	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #208
0x00340038	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #14
0xC350DF2D	medium	METHOD_IN_DIRECT	CUSTOM_MSI Function #1995
0x8273E076	medium	METHOD_OUT_DIRECT	CUSTOM_VIRAGT Function #2077

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	0x615B	0x6200	6.33	CODE, EXEC, READ
.rdata	0x0C34	0x0E00	4	IDATA, READ
.data	0x3CF0	0x0E00	3.8	IDATA, READ, WRITE
.pdata	0x05C4	0x0600	4.25	IDATA, READ
.gfids	0x0004	0x0200	0.02	IDATA, READ
INIT	0x0934	0x0A00	5.01	CODE, EXEC, READ, DISCARD
.rsrc	0x0428	0x0600	2.69	IDATA, READ, DISCARD
.reloc	0x0208	0x0400	3.43	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Enforced
Mitigation score	60 / 100

No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
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.
Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.
Force Integrity - IMAGE_DLLCHARACTERISTICS_FORCE_INTEGRITY is set - the OS validates the signature before loading.

YARA rule matches (2)

Rule	Severity	Detects
PUA_VULN_Driver_Wellbiacomcoltd_Xhuntersys_Xigncode_E727	medium	Detects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - xhunter1.sys. Investigate matches in context: expected filenames or standard...
SUSP_Callbacks	medium	Kernel callback registration

MITRE ATT&CK techniques (15)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1014	Rootkit	Defense Evasion
T1055.001	Process Injection: DLL Injection	Defense Evasion
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1211	Exploitation for Defense Evasion	Defense Evasion
T1489	Service Stop	Impact
T1543.003	Windows Service	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1562.001	Impair Defenses	Defense Evasion
T1562.006	Indicator Blocking	Defense Evasion
T1564.001	Hidden Files and Directories	Defense Evasion
T1569.002	System Services: Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Symantec Time Stamping Services CA - G2
Signer organisation	Symantec Corporation
Issuer	Thawte Timestamping CA
Serial	7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from	2012-12-21 00:00 UTC
Valid until	2020-12-30 23:59 UTC (expired)
Signature validity	Not verified

Certificate revision: 0x0200
Certificate type: PKCS#7
Chain: Symantec Time Stamping Services Signer - G4
Chain: Wellbia.com Co., Ltd.
Chain: Symantec Class 3 SHA256 Code Signing CA
Chain: VeriSign Class 3 Public Primary Certification Authority - G5

Symbolic execution

Engine angr, status static_approximation, 0 paths explored at a maximum depth of 0. 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 xhunter1.sys

Is xhunter1.sys safe?

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

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

What is xhunter1.sys?

xhunter1.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Symantec Time Stamping Services CA - G2.