PhlashNT_64.sys - Vulnerable (72/100) - DriverShield Analysis

Analysis of PhlashNT_64.sys: vulnerable verdict, risk score 72/100. 3 YARA matches, 0/74 multi-engine detections. SHA256 65db1b259e305a52. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

PhlashNT_64.sys - Analysis Report

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

VerdictVulnerable (72/100)
YARA matches3
Multi-engine detections0 / 74
File size61496 bytes
Code-signing signerVeriSign Time Stamping Services Signer - G2
Analyzed2026-09-06
SHA25665db1b259e305a52042e07e111f4fa4af16542c8bacd33655f753ef642228890
SHA1c6d349823bbb1f5b44bae91357895dba653c5861
MD5e9e786bdba458b8b4f9e93d034f73d00

Driver identity

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

File descriptionSWinFlash Driver for Windows NT
ProductWinPhlash
CompanyPhoenix Technologies, Ltd.
Original filenamePHLASHNT.SYS
Internal namePHLASHNT
File version1.6.1.0
Copyright(c) Phoenix Technologies, Ltd. 2000-2003

How the 72/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 matches85 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface48 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (11)

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

APIRiskWhy it matters
MmMapLockedPagescriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmUnmapIoSpacemediumModerate risk - system modification capability
DbgPrintlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign

IOCTL dispatch codes (16)

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
0x008090FFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1087
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080BA66mediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #3737
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00808889mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #546
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00342444mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2321
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x0080C181mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #96
0x00800038mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #14
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x00346F0DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3011
0x0034930DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1219
0x00802528mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2378
0x0080B841mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3600
0x00340306mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #193

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0xB6170xB8005.62CODE, EXEC, READ
.rdata0x04780x06003.16IDATA, READ
.data0x08CC0x04001.48IDATA, READ, WRITE
.pdata0x05340x06003.86IDATA, READ
INIT0x02120x04002.98CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03680x04002.92IDATA, READ, DISCARD
.reloc0x00DC0x02000.85IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLRNot enabled
DEPNot enabled
Integrity checkNot enforced
Mitigation score5 / 100

YARA rule matches (3)

RuleSeverityDetects
PUA_VULN_Driver_Phoenixtechnologiesltd_Phlashnt_Winphlash_65DBmediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - PhlashNT.sys. Investigate matches in context: expected filenames or standard...
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (12)

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
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerVeriSign Time Stamping Services Signer - G2
Signer organisationVeriSign, Inc.
IssuerVeriSign Time Stamping Services CA
Serial3825D7FAF861AF9EF490E726B5D65AD5
Valid from2007-06-15 00:00 UTC
Valid until2012-06-14 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 18 paths explored at a maximum depth of 18. Vulnerability classes reached: 1. 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 PhlashNT_64.sys

Is PhlashNT_64.sys safe?

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

What is the risk score of PhlashNT_64.sys?

PhlashNT_64.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 65db1b259e305a52042e07e111f4fa4af16542c8bacd33655f753ef642228890.

What is PhlashNT_64.sys?

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

Related: Other drivers signed by VeriSign Time Stamping Services Signer - 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