wamsdk.sys - Vulnerable (78/100) - DriverShield Analysis

Analysis of wamsdk.sys: vulnerable verdict, risk score 78/100. 4 YARA matches, 28/75 multi-engine detections. SHA256 5af1dae21425dda8. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

wamsdk.sys - Analysis Report

DriverShield analyzed the Windows kernel driver wamsdk.sys and assigned a verdict of Vulnerable with a composite risk score of 78/100, indicating a known or likely vulnerability surface (60-79 band).

VerdictVulnerable (78/100)
YARA matches4
Multi-engine detections28 / 75
File size192440 bytes
Code-signing signerGlobalSign
Analyzed2026-09-06
SHA2565af1dae21425dda8311a2044209c308525135e1733eeff5dd20649946c6e054c
SHA196f0dbf52aed0afd43e44500116b04b674f7358e
MD5b6b51508ad6f462c45fe102c85d246c8

Driver identity

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

File descriptionWatchDog Antimalware Driver
Productwamsdk
CompanyWatchDogDevelopment.com, LLC.
Original filenamewamsdk.sys
Internal namewamsdk.sys
File version1.1.100
CopyrightCopyright (C) 2025

How the 78/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 surface100 / 100
Known-vulnerable corpus100 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (41)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsSetCreateProcessNotifyRoutinehighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutineExhighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
ObRegisterCallbackshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwWriteFilemediumModerate risk - system modification capability
NtQuerySystemInformationmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
CmRegisterCallbackmediumModerate risk - system modification capability
ZwDeleteFilemediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwQueryInformationFilelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
ProbeForWritelowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 41 resolved.

IOCTL dispatch codes (35)

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
0x00343673highMETHOD_NEITHERFILE_DEVICE_DISK Function #3484
0x00345453highMETHOD_NEITHERFILE_DEVICE_DISK Function #1300
0x00345243highMETHOD_NEITHERFILE_DEVICE_DISK Function #1168
0x0080083BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #526
0x0022015BhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #86
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00343D3EmediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #3919
0x0080B8F8mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3646
0x00802824mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2569
0x00343D50mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #3924
0x0080BFE8mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #4090
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00808789mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #482
0x0022BF36mediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #4045
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x00220FE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1018
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x00800400mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #256
0x00800080mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #32
0x00800100mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #64
0x00800200mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #128
0x00800008mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2
0x00343152mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #3156
0x00344D4DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #851

Showing 24 of 35 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
.text0x19B350x19C006.16CODE, EXEC, READ
.rdata0x76300x78004.83IDATA, READ
.data0x50D480x3E005.4IDATA, READ, WRITE
.pdata0x06CC0x08004.47IDATA, READ
PAGE0x1C4F0x1E006.11CODE, EXEC, READ
INIT0x11B60x12005.19CODE, EXEC, READ, DISCARD
.rsrc0x03500x04002.84IDATA, READ, DISCARD
.reloc0x007C0x02001.68IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score100 / 100

YARA rule matches (4)

RuleSeverityDetects
PUA_VULN_Driver_Watchdogdevelopmentcomllc_Wamsdksys_Wamsdk_0BE8mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - wamsdk.sys. Investigate matches in context: expected filenames or standard v...
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
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1014RootkitDefense Evasion
T1055.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
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.001Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerGlobalSign
Signer organisationGlobalSign
IssuerGlobalSign Root CA
Serial1EE5F169DFF97352B6465D66A
Valid from2018-09-19 00:00 UTC
Valid until2028-01-28 12:00 UTC
Signature validityVerified

Symbolic execution

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

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

Is wamsdk.sys safe?

Based on DriverShield static and dynamic analysis, wamsdk.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 78/100 (verdict: vulnerable). Always validate findings independently before acting.

What is the risk score of wamsdk.sys?

wamsdk.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: 5af1dae21425dda8311a2044209c308525135e1733eeff5dd20649946c6e054c.

What is wamsdk.sys?

wamsdk.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by GlobalSign.

Related: Other drivers signed by GlobalSign · 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