Analysis of IntelTA.sys: clean verdict, risk score 20/100. 1 YARA match. SHA256 087d150cf044e4fe. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver IntelTA.sys and assigned a verdict of Clean with a composite risk score of 20/100, indicating no notable risk signals (0-29 band).
| Verdict | Clean (20/100) |
| YARA matches | 1 |
| File size | 27784 bytes |
| Code-signing signer | Microsoft Windows Hardware Abstraction Layer Publisher |
| Analyzed | 2026-03-22 |
| SHA256 | 087d150cf044e4feccd4583ab6b88b5d183d8b8f98434169a3dc346a7a23205c |
| SHA1 | ea6e8435d655b4b7c931195486b48586bfa5b034 |
| MD5 | 05d60356184c95b353a16ddb7830eadc |
Version resource data embedded in the IntelTA.sys PE header, as extracted by the analysis engine.
| File description | Intel Telemetry Driver |
|---|---|
| Product | Microsoft® Windows® Operating System |
| Company | Microsoft Corporation |
| Original filename | IntelTA.sys |
| Internal name | IntelTA.sys |
| File version | 10.0.19041.3636 (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 | 30 / 100 |
| Dangerous kernel imports | 45 / 100 |
| IOCTL dispatch surface | 30 / 100 |
| Known-vulnerable corpus | 0 / 100 |
| Code-signing state | 80 / 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 IntelTA.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| MmUnmapIoSpace | medium | Moderate risk - system modification capability |
| DbgPrintEx | low | Standard kernel API - generally benign |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
| KeInitializeEvent | low | Standard kernel API - generally benign |
| KeWaitForSingleObject | 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 |
|---|---|---|---|
| 0x0080002F | high | METHOD_NEITHER | FILE_DEVICE_CUSTOM Function #11 |
| 0x0080958B | high | METHOD_NEITHER | FILE_DEVICE_CUSTOM Function #1378 |
| 0x00808D8B | high | METHOD_NEITHER | FILE_DEVICE_CUSTOM Function #866 |
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x00800020 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #8 |
| 0x00223414 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #3333 |
| 0x0022011C | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #71 |
| 0x00802494 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2341 |
| 0x00228341 | medium | METHOD_IN_DIRECT | FILE_DEVICE_UNKNOWN Function #208 |
| 0x00340398 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #230 |
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 | 0x0CE9 | 0x0E00 | 5.77 | CODE, EXEC, READ |
| .rdata | 0x0FA0 | 0x1000 | 5.22 | IDATA, READ |
| .data | 0x03A0 | 0x0200 | 0.82 | IDATA, READ, WRITE |
| .pdata | 0x0150 | 0x0200 | 2.74 | IDATA, READ |
| .idata | 0x036E | 0x0400 | 3.71 | IDATA, READ |
| PAGE | 0x0E81 | 0x1000 | 5.77 | CODE, EXEC, READ |
| INIT | 0x022A | 0x0400 | 3.86 | CODE, EXEC, READ, DISCARD |
| GFIDS | 0x0028 | 0x0200 | 0.38 | IDATA, READ, DISCARD |
| .rsrc | 0x0400 | 0x0400 | 3.38 | IDATA, READ, DISCARD |
| .reloc | 0x014C | 0x0200 | 3.44 | IDATA, READ, DISCARD |
| Control Flow Guard | Enabled |
|---|---|
| ASLR | Enabled |
| DEP | Enabled |
| Integrity check | Not enforced |
| Mitigation score | 85 / 100 |
| Rule | Severity | Detects |
|---|---|---|
| SUSP_PhysMem | high | Physical memory mapping |
Techniques this driver could enable if loaded by an adversary.
| ID | Technique | Tactic |
|---|---|---|
| T1003.001 | OS Credential Dumping: LSASS Memory | Credential Access |
| T1055.012 | Process Hollowing | Defense Evasion |
| T1068 | Exploitation for Privilege Escalation | Privilege Escalation |
| T1071 | Application Layer Protocol | Command and Control |
| T1211 | Exploitation for Defense Evasion | Defense Evasion |
| T1543.003 | Windows Service | Persistence |
| T1553.002 | Subvert Trust Controls: Code Signing | Defense Evasion |
| T1569.002 | Service Execution | Execution |
| T1652 | Device Driver Discovery | Discovery |
| Signer | Microsoft Windows Hardware Abstraction Layer Publisher |
|---|---|
| Signer organisation | Microsoft Corporation |
| Issuer | Microsoft Code Signing PCA 2010 |
| Serial | 3300000509137EF52CBCCCBF57000000000509 |
| Valid from | 2023-02-16 20:11 UTC |
| Valid until | 2024-01-31 20:11 UTC (expired) |
| Signature validity | Not verified |
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, IntelTA.sys is assessed as clean, with no notable risk signals. Its composite risk score is 20/100 (verdict: clean). Always validate findings independently before acting.
IntelTA.sys has a DriverShield composite risk score of 20/100, placing it in the clean verdict band. SHA256: 087d150cf044e4feccd4583ab6b88b5d183d8b8f98434169a3dc346a7a23205c.
IntelTA.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Microsoft Windows Hardware Abstraction Layer Publisher.
Related: Other drivers signed by Microsoft Windows Hardware Abstraction Layer Publisher · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas