Closed badboycxcc closed 2 months ago
The bootkit does not open filecrypt.sys. It adds an entry to BootDriverListHead so that the Windows bootloader will attempt to load it as a core driver. When it does that, the bootkit intercepts the disk read interrupt and provides the bootkit's custom driver instead. Once the custom driver is executed it removes the extra entry so filecrypt.sys will be properly loaded after kernel initialization.
Is this how it works?
ok
What is the function of opening the C:\Windows\System32\drivers\filecrypt.sys file? How to load your own sys file?