amifldrv64.sys - Malicious (88/100) - DriverShield Analysis

Analysis of amifldrv64.sys: malicious verdict, risk score 88/100. 2 YARA matches, 1/76 multi-engine detections. SHA256 fda506e2aa85dc41. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

amifldrv64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver amifldrv64.sys and assigned a verdict of Malicious with a composite risk score of 88/100, indicating malicious indicators (80-100 band).

VerdictMalicious (88/100)
YARA matches2
Multi-engine detections1 / 76
File size15472 bytes
Code-signing signerVeriSign Time Stamping Services Signer - G2
Analyzed2026-09-06
SHA256fda506e2aa85dc41a4cbc23d3ecc71ab34e06f1def736e58862dc449acbc2330
SHA141f2d0f9863bce8920c207b1ef5d3d32b603edef
MD5cb6173824b31a721e5cf332c75bb2473

How the 88/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 matches80 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface3 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference40 / 100

Kernel imports (14)

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

APIRiskWhy it matters
MmMapLockedPagescriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemoryhighPotentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandlemediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign

IOCTL dispatch codes (1)

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
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x11760x12005.91CODE, EXEC, READ
.rdata0x02780x04003.11IDATA, READ
.data0x01100x02000.3IDATA, READ, WRITE
.pdata0x00B40x02001.54IDATA, READ
INIT0x036E0x04004.41CODE, EXEC, READ, WRITE, DISCARD

Exploit mitigations

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

YARA rule matches (2)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (10)

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
T1543.003Windows ServicePersistence
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

Associated CVEs

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

Is amifldrv64.sys safe?

Based on DriverShield static and dynamic analysis, amifldrv64.sys is flagged as malicious and should be treated as dangerous. Its composite risk score is 88/100 (verdict: malicious). Always validate findings independently before acting.

What is the risk score of amifldrv64.sys?

amifldrv64.sys has a DriverShield composite risk score of 88/100, placing it in the malicious verdict band. SHA256: fda506e2aa85dc41a4cbc23d3ecc71ab34e06f1def736e58862dc449acbc2330.

What is amifldrv64.sys?

amifldrv64.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 · CVE-2019-18670 · 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