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

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

zamguard64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver zamguard64.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 detections22 / 75
File size203680 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-09-06
SHA256543991ca8d1c65113dff039b85ae3f9a87f503daec30f46929fd454bc57e5a91
SHA116d7ecf09fc98798a6170e4cef2745e0bee3f5c7
MD521e13f2cb269defeae5e1d09887d47bb

Driver identity

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

File descriptionZAM
ProductZAM
CompanyZemana Ltd.
CopyrightZemana Ltd. All rights reserved.

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 state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (42)

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

APIRiskWhy it matters
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ObRegisterCallbackshighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutineExhighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutinehighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
CmRegisterCallbackmediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
NtQuerySystemInformationmediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
ZwDeleteFilemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ZwWriteFilemediumModerate risk - system modification capability
ProbeForReadlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 42 resolved.

IOCTL dispatch codes (40)

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
0x00343D43highMETHOD_NEITHERFILE_DEVICE_DISK Function #3920
0x0080BACFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3763
0x002215FFhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #1407
0x00343673highMETHOD_NEITHERFILE_DEVICE_DISK Function #3484
0x00345453highMETHOD_NEITHERFILE_DEVICE_DISK Function #1300
0x00345243highMETHOD_NEITHERFILE_DEVICE_DISK Function #1168
0x0034011FhighMETHOD_NEITHERFILE_DEVICE_DISK Function #71
0x0080083BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #526
0x0022015BhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #86
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080FA81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3744
0x0080B941mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3664
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x008008ACmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #555
0x00802824mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2569
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x008024ACmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2347
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00342444mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2321
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x0022058DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #355
0x0022BF00mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #4032
0x0022EFE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3066
0x00221846mediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #1553

Showing 24 of 40 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
.text0x217B50x218006.32CODE, EXEC, READ
.hook0x09AF0x0A005.04CODE, EXEC, READ, WRITE
.rdata0x47440x48005.49IDATA, READ
.data0x53C880x68004.89IDATA, READ, WRITE
.pdata0x08D00x0A004.69IDATA, READ
INIT0x11060x12005.15CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x02680x04002.07IDATA, READ, DISCARD
.reloc0x00600x02001.21IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (4)

RuleSeverityDetects
PUA_VULN_Driver_Zemanaltd_Zam_5439mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - zam64.sys, zamguard32.sys, zamguard64.sys. Investigate matches in context: e...
BYOVD_ProcKillcriticalProcess termination EDR killer
SUSP_CallbacksmediumKernel callback registration
MAL_EDRKillercriticalGeneric EDR killer pattern

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.001Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerSymantec Time Stamping Services CA - G2
Signer organisationSymantec Corporation
IssuerThawte Timestamping CA
Serial7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from2012-12-21 00:00 UTC
Valid until2020-12-30 23:59 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 zamguard64.sys

Is zamguard64.sys safe?

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

zamguard64.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: 543991ca8d1c65113dff039b85ae3f9a87f503daec30f46929fd454bc57e5a91.

What is zamguard64.sys?

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

Related: Other drivers signed by Symantec Time Stamping Services CA - G2 · 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