Analysis of amdi2c.sys: clean verdict, risk score 24/100. 1 YARA match. SHA256 387811d57def06c9. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver amdi2c.sys and assigned a verdict of Clean with a composite risk score of 24/100, indicating no notable risk signals (0-29 band).
| Verdict | Clean (24/100) |
| YARA matches | 1 |
| File size | 45568 bytes |
| Analyzed | 2026-03-22 |
| SHA256 | 387811d57def06c9736d9f0bab0dfb0f83dbab19e5489bf9a6dcdcbd682dd8fe |
| SHA1 | 3bc822eff605ee91c84902a71659e1f52ead9660 |
| MD5 | d0e26e590de1424ccc4f77d1687049ef |
Version resource data embedded in the amdi2c.sys PE header, as extracted by the analysis engine.
| File description | AMD I2C Controller Driver |
|---|---|
| Product | AMD I2C Controller Driver |
| Company | Advanced Micro Devices, Inc |
| Original filename | amdi2c.sys |
| Internal name | amdi2c.sys |
| File version | 1.2.0.99 |
| Copyright | Copyright © 2014-2019 Advanced Micro Devices, Inc |
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 | 75 / 100 |
| IOCTL dispatch surface | 27 / 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 amdi2c.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| MmMapLockedPagesSpecifyCache | critical | Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination |
| MmGetSystemRoutineAddress | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| MmUnmapIoSpace | medium | Moderate risk - system modification capability |
| IoBuildDeviceIoControlRequest | low | Standard kernel API - generally benign |
| KeWaitForSingleObject | low | Standard kernel API - generally benign |
| RtlInitUnicodeString | low | Standard kernel API - generally benign |
| KeInitializeEvent | 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 |
| 0x002243E8 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #250 |
| 0x0034B941 | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #3664 |
| 0x00802494 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2341 |
| 0x0080EC81 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #2848 |
| 0x0034130D | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #1219 |
| 0x00340126 | medium | METHOD_OUT_DIRECT | FILE_DEVICE_DISK Function #73 |
| 0x00340350 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #212 |
| 0x00340031 | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #12 |
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 | 0x83F3 | 0x8400 | 6.17 | CODE, EXEC, READ |
| .rdata | 0x0C1C | 0x0E00 | 4.38 | IDATA, READ |
| .data | 0x04A8 | 0x0200 | 1.37 | IDATA, READ, WRITE |
| .pdata | 0x03FC | 0x0400 | 4.44 | IDATA, READ |
| .gfids | 0x0004 | 0x0200 | 0.02 | IDATA, READ |
| PAGE | 0x054C | 0x0600 | 5.6 | CODE, EXEC, READ |
| INIT | 0x0442 | 0x0600 | 3.82 | CODE, EXEC, READ, DISCARD |
| .rsrc | 0x0438 | 0x0600 | 2.68 | IDATA, READ, DISCARD |
| .reloc | 0x0038 | 0x0200 | 0.69 | IDATA, READ, DISCARD |
| Control Flow Guard | Not enabled |
|---|---|
| ASLR | Enabled |
| DEP | Enabled |
| Integrity check | Not enforced |
| Mitigation score | 50 / 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 |
| T1553.006 | Code Signing Policy Modification | Defense Evasion |
| 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, amdi2c.sys is assessed as clean, with no notable risk signals. Its composite risk score is 24/100 (verdict: clean). Always validate findings independently before acting.
amdi2c.sys has a DriverShield composite risk score of 24/100, placing it in the clean verdict band. SHA256: 387811d57def06c9736d9f0bab0dfb0f83dbab19e5489bf9a6dcdcbd682dd8fe.
amdi2c.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 · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas