irec.sys
The driver in question, identified as \\.\IREC, provides an interface for external programs to directly interact with system processes. Its key functionality is encapsulated in the OPENPROCESS function which, upon receiving a Process ID (PID), returns a handle to that specific process operating within the kernels domain. The vulnerability emerges from the indiscriminate nature of this functionality. An ill-intentioned actor can exploit this to obtain handles to critical processes like LSASS. With a hardcoded access mask of 0x410, this driver essentially grants PROCESS_QUERY_INFORMATION and PROCESS_VM_READ permissions, enabling unauthorized memory dumps from privileged processes, all from an unprivileged context.
Known samples 1
0 recorded TRUE · 1 recorded FALSE · 0 unknown for loading despite HVCI. Results apply to individual samples.
irec.sysSample 1 · HVCI FALSE
- MD5
f1a203406a680cc7e4017844b129dcbf- SHA1
d2fb46277c36498e87d0f47415b7980440d40e3d- SHA256
dd573f23d656818036fc9ae1064eda31aca86acb9bc44a6e127db3ea112a9094- Imphash
3ee1cb6085fbe05e46e2b88493426848- Authentihash MD5
3a6ceda4dfa265ed536cbabe0f1d4466- Authentihash SHA1
719f659300ba463efeeab5916f0378c64fc1ad4a- Authentihash SHA256
457e2eb5ee1def0e336463b7f62dcc02fdde307b817cf750907a5f5465c4dcb7- Machine
- AMD64
- Version
- Not recorded
- Publisher
- Not recorded
Recorded command
sc.exe create irec binPath=C:\windows\temp\irec.sys type=kernel && sc.exe start irec.sysElevate privileges · Privileges: kernel · OS: Windows 10
Research & references
Acknowledgement: Michael Alfaro (@_mmpte_software), Tyler Booth @tyler_dru1d

