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

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

TmComm.sys - Analysis Report

DriverShield analyzed the Windows kernel driver TmComm.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 matches4
Multi-engine detections1 / 74
File size454264 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-09-06
SHA256cc687fe3741bbde1dd142eac0ef59fd1d4457daee43cdde23bb162ef28d04e64
SHA1a00e444120449e35641d58e62ed64bb9c9f518d2
MD52e1f8a2a80221deb93496a861693c565

Driver identity

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

File descriptionTrendMicro Common Module
Product쳌쳌쳌쳌SystemRoot
CompanyTrend Micro Inc.
Original filenameTmComm.sys
Internal nameTmComm.sys
File version7.30.0.1099
CopyrightCopyright (C) 2018 Trend Micro Incorporated. All rights reserved.

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 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 (45)

Kernel-mode APIs resolved from the Import Address Table of TmComm.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
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutinehighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwSetInformationFilemediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
PsSetCreateThreadNotifyRoutinemediumModerate risk - system modification capability
ZwWriteFilemediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
IoCreateDeviceSecurelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
SeAccessChecklowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 45 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
0x0080898BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #610
0x0080808BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #34
0x0080850FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #323
0x008090FFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1087
0x0080840FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #259
0x008025FFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2431
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x003437E8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #3578
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x0022C7E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #506
0x00808839mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #526
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x00800050mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #20
0x00349FE8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2042
0x0034247CmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2335
0x00808189mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #98
0x00802824mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2569
0x0022E800mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2560
0x0080B841mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3600
0x0080BA00mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3712
0x00342444mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2321
0xC3504C24mediumMETHOD_BUFFEREDCUSTOM_MSI Function #777
0xC3504824mediumMETHOD_BUFFEREDCUSTOM_MSI Function #521

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
.text0x536450x538005.88CODE, EXEC, READ
.rdata0x61740x62003.44IDATA, READ
.data0x33FC0x16004.68IDATA, READ, WRITE
.pdata0x3AE00x3C005.52IDATA, READ
.gfids0x00040x02000.06IDATA, READ
PAGE0x1AE40x1C006.18CODE, EXEC, READ
.edata0x58340x5A005.8IDATA, READ
INIT0x18900x1A005.17CODE, EXEC, READ, DISCARD
.rsrc0x05680x06003.12IDATA, READ, DISCARD
.reloc0x04C80x06004.86IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (4)

RuleSeverityDetects
PUA_VULN_Driver_Trendmicroinc_Tmcommsys_Trendmicroeyes_CC68mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - TmComm.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 (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 static_approximation, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. Exploitable paths: 1.

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

Is TmComm.sys safe?

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

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

What is TmComm.sys?

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