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

Analysis of truesight.sys: suspicious verdict, risk score 58/100. 1 YARA match, 28/74 multi-engine detections. SHA256 bfc2ef3b404294fe. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

truesight.sys - Analysis Report

DriverShield analyzed the Windows kernel driver truesight.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 matches1
Multi-engine detections28 / 74
File size53696 bytes
Code-signing signerSectigo Public Code Signing Root R46
Analyzed2026-03-24
SHA256bfc2ef3b404294fe2fa05a8b71c7f786b58519175b7202a69fe30f45e607ff1c
SHA1363068731e87bcee19ad5cb802e14f9248465d31
MD5f53fa44c7b591a2be105344790543369

Driver identity

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

File descriptionRogueKiller Antirootkit Driver
ProductTruesight
CompanyAdlice Software
Original filenameTruesight
Internal nameTruesight
File version3.3.0
CopyrightCopyright Adlice Software(C) 2023

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

Kernel imports (26)

Kernel-mode APIs resolved from the Import Address Table of truesight.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
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwSetValueKeymediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
IoCreateSymbolicLinklowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
IofCompleteRequestlowStandard 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
0x0080840FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #259
0x00343D07highMETHOD_NEITHERFILE_DEVICE_DISK Function #3905
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0022D3E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1274
0x0080B941mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3664
0x0022DC00mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1792
0x0022DB25mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1737
0x00220B15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #709
0x0022E8CEmediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #2611
0x0080BA48mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3730
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x0022B941mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3664
0x0034037CmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #223
0x00220068mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #26
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
.text0x2DD40x2E006.24CODE, EXEC, READ
.rdata0x11840x12004.6IDATA, READ
.data0x03200x04002.02IDATA, READ, WRITE
.pdata0x04440x06003.28IDATA, READ
PAGE0x1CBC0x1E006.13CODE, EXEC, READ
INIT0x0B140x0C005.24CODE, EXEC, READ, DISCARD
.rsrc0x03E00x04003.21IDATA, READ, DISCARD
.reloc0x006C0x02001.45IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score100 / 100

YARA rule matches (1)

RuleSeverityDetects
PUA_VULN_Driver_Adlicesoftware_Truesight_Truesight_BFC2mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - truesight.sys

MITRE ATT&CK techniques (14)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
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
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerSectigo Public Code Signing Root R46
Signer organisationSectigo Limited
IssuerAAA Certificate Services
Serial48FC93B46055948D36A7C98A89D69416
Valid from2021-05-25 00:00 UTC
Valid until2028-12-31 23:59 UTC
Signature validityVerified

Symbolic execution

Engine angr, status static_approximation, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. Exploitable paths: 10.

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

Is truesight.sys safe?

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

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

What is truesight.sys?

truesight.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Sectigo Public Code Signing Root R46.

Related: Other drivers signed by Sectigo Public Code Signing Root R46 · 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