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

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

mtcBSv64.sys - Analysis Report

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

VerdictSuspicious (58/100)
YARA matches2
Multi-engine detections1 / 76
File size78336 bytes
Code-signing signerSymantec Class 3 Extended Validation Code Signing CA - G2
Analyzed2026-09-06
SHA256ff803017d1acafde6149fe7d463aee23b1c4f6f3b97c698c05f3ca6f07e4df6c
SHA1cde32654a041fedc7b0fa1083f6005b950760062
MD5ae0e3f25a7a4b29f3f16128303b264ec

Driver identity

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

File descriptionGetac System Service Provider
ProductGetac System Service Provider
CompanyGetac Technology Corporation
Original filenamemtcBSv64.sys
Internal namemtcBSv64.sys
File version21, 1, 6, 3
CopyrightCopyright (C) 2012 Getac Technology Corporation

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.

ComponentSub-score
Multi-engine consensus0 / 100
YARA signature matches80 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface21 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (13)

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

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

IOCTL dispatch codes (7)

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
0x0034B828mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #3594
0x008000B9mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #46
0x0080F881mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3616
0x00340370mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #220
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13
0x008002A2mediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #168

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x39020x3A006.47CODE, EXEC, READ
.rdata0x0FEC0x10005.1IDATA, READ
.data0x03240x04002.45IDATA, READ, WRITE
.pdata0x039C0x04003.88IDATA, READ
.gfids0x00040x02000.02IDATA, READ
PAGE0x204E0x22006.26CODE, EXEC, READ
INIT0x06020x08004.43CODE, EXEC, READ, DISCARD
.rsrc0x05C00x06003.31IDATA, READ, DISCARD
.reloc0x00BC0x02002.32IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score55 / 100

YARA rule matches (2)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (11)

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
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerSymantec Class 3 Extended Validation Code Signing CA - G2
Signer organisationSymantec Corporation
IssuerVeriSign Class 3 Public Primary Certification Authority - G5
Serial191A32CB759C97B8CFAC118DD5127F49
Valid from2014-03-04 00:00 UTC
Valid until2024-03-03 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.

Frequently asked questions about mtcBSv64.sys

Is mtcBSv64.sys safe?

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

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

What is mtcBSv64.sys?

mtcBSv64.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 Class 3 Extended Validation Code Signing CA - G2.

Related: Other drivers signed by Symantec Class 3 Extended Validation Code Signing 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