Analysis of mspclock.sys: clean verdict, risk score 11/100. 0 YARA matches. SHA256 6e5daa5d9826a316. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver mspclock.sys and assigned a verdict of Clean with a composite risk score of 11/100, indicating no notable risk signals (0-29 band).
| Verdict | Clean (11/100) |
| YARA matches | 0 |
| File size | 11264 bytes |
| Analyzed | 2026-03-22 |
| SHA256 | 6e5daa5d9826a3165514ce2ac4aec23033d7ba993f06d2bdffc68052ca71c4a0 |
| SHA1 | 05095f7fff2eb7f6a57219febc2cc318ba27335d |
| MD5 | 4b5cd00deab6bc5fe650d5e90ba5719a |
Version resource data embedded in the mspclock.sys PE header, as extracted by the analysis engine.
| File description | MS Proxy Clock |
|---|---|
| Product | Microsoft® Windows® Operating System |
| Company | Microsoft Corporation |
| Original filename | mspclock.sys |
| Internal name | mspclock.sys |
| File version | 10.0.19041.1 (WinBuild.160101.0800) |
| Copyright | © Microsoft Corporation. All rights reserved. |
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 | 0 / 100 |
| Dangerous kernel imports | 39 / 100 |
| IOCTL dispatch surface | 9 / 100 |
| Known-vulnerable corpus | 0 / 100 |
| Code-signing state | 50 / 100 |
| Packing and entropy | 0 / 100 |
| Dynamic behaviour | 0 / 100 |
| CVE cross-reference | 0 / 100 |
Kernel-mode APIs resolved from the Import Address Table of mspclock.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| IofCompleteRequest | low | Standard kernel API - generally benign |
| ExFreePool | low | Standard kernel API - generally benign |
| KeInitializeEvent | low | Standard kernel API - generally benign |
| IoCreateDevice | low | Standard kernel API - generally benign |
| IoDeleteDevice | low | Standard kernel API - generally benign |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
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 |
|---|---|---|---|
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x00340072 | medium | METHOD_OUT_DIRECT | FILE_DEVICE_DISK Function #28 |
| 0x00340384 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #225 |
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 | 0x0175 | 0x0200 | 2.16 | CODE, EXEC, READ |
| .rdata | 0x0748 | 0x0800 | 2.63 | IDATA, READ |
| .data | 0x0090 | 0x0200 | 0.28 | IDATA, READ, WRITE |
| .pdata | 0x00FC | 0x0200 | 1.98 | IDATA, READ |
| .idata | 0x0712 | 0x0800 | 4.01 | IDATA, READ |
| .guids | 0x0020 | 0x0200 | 0.54 | IDATA, READ |
| PAGE | 0x04E4 | 0x0600 | 4.83 | CODE, EXEC, READ |
| INIT | 0x0102 | 0x0200 | 3.25 | CODE, EXEC, READ, DISCARD |
| GFIDS | 0x0044 | 0x0200 | 0.6 | IDATA, READ, DISCARD |
| .rsrc | 0x03F8 | 0x0400 | 3.27 | IDATA, READ, DISCARD |
| .reloc | 0x013C | 0x0200 | 3.23 | IDATA, READ, DISCARD |
| Control Flow Guard | Enabled |
|---|---|
| ASLR | Enabled |
| DEP | Enabled |
| Integrity check | Not enforced |
| Mitigation score | 80 / 100 |
Techniques this driver could enable if loaded by an adversary.
| ID | Technique | Tactic |
|---|---|---|
| T1211 | Exploitation for Defense Evasion | Defense Evasion |
| T1543.003 | Windows Service | Persistence |
| T1553.002 | Subvert Trust Controls: Code Signing | Defense Evasion |
| T1553.006 | Code Signing Policy Modification | Defense Evasion |
| T1569.002 | System Services: Service Execution | Execution |
| T1652 | Device Driver Discovery | Discovery |
Engine angr, status no_findings, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. Exploitable paths: 0.
Based on DriverShield static and dynamic analysis, mspclock.sys is assessed as clean, with no notable risk signals. Its composite risk score is 11/100 (verdict: clean). Always validate findings independently before acting.
mspclock.sys has a DriverShield composite risk score of 11/100, placing it in the clean verdict band. SHA256: 6e5daa5d9826a3165514ce2ac4aec23033d7ba993f06d2bdffc68052ca71c4a0.
mspclock.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators.
Related: What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas