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

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

window.sys - Analysis Report

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

Verdict	Malicious (88/100)
YARA matches	2
Multi-engine detections	8 / 76
File size	82848 bytes
Code-signing signer	Symantec Time Stamping Services CA - G2
Analyzed	2026-04-02
SHA256	58a74dceb2022cd8a358b92acd1b48a5e01c524c3b0195d7033e4bd55eff4495
SHA1	05c0c49e8bcf11b883d41441ce87a2ee7a3aba1d
MD5	43830326cd5fae66f5508e27cbec39a0

Driver identity

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

File description	VirIT Agent System
Product	VirIT Agent System
Company	TG Soft S.a.s.
Original filename	viragt64.sys
Internal name	viragt.sys
File version	1, 0, 0, 11
Copyright	Copyright (C) TG Soft S.a.s. 2011, 2016 - www.tgsoft.it

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.

Component	Sub-score
Multi-engine consensus	0 / 100
YARA signature matches	55 / 100
Dangerous kernel imports	100 / 100
IOCTL dispatch surface	100 / 100
Known-vulnerable corpus	100 / 100
Code-signing state	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (27)

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

API	Risk	Why it matters
MmMapLockedPagesSpecifyCache	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwTerminateProcess	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwOpenProcess	high	Potentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
ZwSetInformationFile	medium	Moderate risk - system modification capability
ZwCreateKey	medium	Moderate risk - system modification capability
ZwDeleteKey	medium	Moderate risk - system modification capability
ZwSetValueKey	medium	Moderate risk - system modification capability
ZwQuerySystemInformation	medium	Moderate risk - system modification capability
KeBugCheckEx	medium	Moderate risk - system modification capability
ZwWriteFile	medium	Moderate risk - system modification capability
IoCreateSymbolicLink	low	Standard kernel API - generally benign
ZwReadFile	low	Standard kernel API - generally benign
ZwQueryValueKey	low	Standard kernel API - generally benign
RtlInitAnsiString	low	Standard kernel API - generally benign
ZwOpenKey	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
ZwCreateFile	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign
ZwQueryInformationFile	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
KeDelayExecutionThread	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign

IOCTL dispatch codes (27)

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.

Code	Severity	Transfer	Description
0x82730030	critical (known exploit)	METHOD_BUFFERED	Arbitrary process kill (viragt64)
0x008000BF	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #47
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x00343D00	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #3904
0x00802484	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2337
0x008024BC	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2351
0x0080248C	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2339
0x00800020	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #8
0x82730028	medium	METHOD_BUFFERED	CUSTOM_VIRAGT Function #10
0x82730008	medium	METHOD_BUFFERED	CUSTOM_VIRAGT Function #2
0x8273001C	medium	METHOD_BUFFERED	CUSTOM_VIRAGT Function #7
0x82730038	medium	METHOD_BUFFERED	CUSTOM_VIRAGT Function #14
0x82730050	medium	METHOD_BUFFERED	CUSTOM_VIRAGT Function #20
0x82730070	medium	METHOD_BUFFERED	CUSTOM_VIRAGT Function #28
0x82730068	medium	METHOD_BUFFERED	CUSTOM_VIRAGT Function #26
0x82730080	medium	METHOD_BUFFERED	CUSTOM_VIRAGT Function #32
0x8273009C	medium	METHOD_BUFFERED	CUSTOM_VIRAGT Function #39
0x82730094	medium	METHOD_BUFFERED	CUSTOM_VIRAGT Function #37
0x827300B4	medium	METHOD_BUFFERED	CUSTOM_VIRAGT Function #45
0x00800C84	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #801
0x0080972D	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #1483
0x002203E8	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #250
0x00802494	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2341
0x00802824	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2569

Showing 24 of 27 extracted control codes.

PE sections

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

Section	Virtual size	Raw size	Entropy	Flags
.text	0xD05A	0xD200	6.36	CODE, EXEC, READ
.rdata	0x0C58	0x0E00	4.54	IDATA, READ
.data	0x3960	0x0200	0.93	IDATA, READ, WRITE
.pdata	0x036C	0x0400	3.88	IDATA, READ
INIT	0x0842	0x0A00	4.56	CODE, EXEC, READ, WRITE, DISCARD
.rsrc	0x0438	0x0600	2.52	IDATA, READ, DISCARD
.reloc	0x014C	0x0200	1.65	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Not enabled
DEP	Not enabled
Integrity check	Not enforced
Mitigation score	5 / 100

• No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
• No ASLR - ASLR is disabled. The driver loads at a predictable address, enabling reliable exploitation of memory corruption vulnerabilities.
• No DEP - DEP is disabled. Data pages are executable, allowing shellcode execution from stack/heap buffers.
• Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

YARA rule matches (2)

Rule	Severity	Detects
PUA_VULN_Driver_Tgsoftsas_Viragtsys_Viritagentsystem_58A7	medium	Detects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - viraglt64.sys, viragt64.sys
VULN_Viragt	critical	viragt64.sys Kasseika ransomware

MITRE ATT&CK techniques (14)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1055.001	Process Injection: DLL Injection	Defense Evasion
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1112	Modify Registry	Defense Evasion
T1211	Exploitation for Defense Evasion	Defense Evasion
T1489	Service Stop	Impact
T1543.003	Windows Service	Persistence
T1547.001	Registry Run Keys	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1562.001	Disable/Modify Tools	Defense Evasion
T1569.002	Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Symantec Time Stamping Services CA - G2
Signer organisation	Symantec Corporation
Issuer	Thawte Timestamping CA
Serial	7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from	2012-12-21 00:00 UTC
Valid until	2020-12-30 23:59 UTC (expired)
Signature validity	Not verified

• Certificate revision: 0x0200
• Certificate type: PKCS#7
• Chain: Symantec Time Stamping Services Signer - G4
• Chain: VeriSign Class 3 Public Primary Certification Authority - G5
• Chain: TG Soft S.a.s. Di Tonello Gianfranco e C.
• Chain: VeriSign Class 3 Code Signing 2010 CA

Symbolic execution

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

Is window.sys safe?

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

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

What is window.sys?

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