Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[help] path problem - driver not loaded #10

Open
valeita opened this issue Feb 13, 2019 · 8 comments
Open

[help] path problem - driver not loaded #10

valeita opened this issue Feb 13, 2019 · 8 comments

Comments

@valeita
Copy link

valeita commented Feb 13, 2019

Hi, i'm trying to build a dkom following your guide and using your code.
I followed all step, but when i use the .exe, and error occurred.
schermata 2019-02-13 alle 08 20 19
I used Visual studio 2017, latest version of SDK (version 1809) and WDK (version 1809). The building in Visual Studio not give me problem and create the Rootkit.sys. Then, thinking that the problem is the path, i copy this in every position of my computer, and try to modify the path in loader.c many times, but the error is unresolved. I try to build it as 64bit or 32bit, but nothing has changed. I'm seeing the code in loader.c, and i think that the problem is the starting of service. Do you have any idea? What are blocking the createservice?
I'm trying it in VM windows 7, 64bit.
Thanks in advance.

@valeita
Copy link
Author

valeita commented Feb 13, 2019

i Forgot, sorry for the italian output, the error is: "Impossibile to find the path specified"

@yangsystem
Copy link

Same problem here. Any info on fixing it?

@valeita
Copy link
Author

valeita commented Mar 25, 2019

Hi man, a penetration tester said me that the problem is the virtual machine. It's impossible create a rootkit for a virtual machine because the disk are virtual and the Hypervisor of, in my case VMWare, can't emulate this type of istructions. I'm not sure about why, but i'm sure today that the problem is the virtual machine. I think that this issue can be closed.

@yangsystem
Copy link

yangsystem commented Mar 25, 2019 via email

@landhb
Copy link
Owner

landhb commented Mar 26, 2019

I'm not sure what you mean by that. There aren't any specific instructions used that wouldn't be emulated by a hypervisor. I just tested this on the latest Windows 10 VM from Microsoft's Edge VM site. It still works fine as long as you set the path correctly when you build the loader, and place the .sys file in that location. Here's a gif I just made performing it on build 17763:

Demo

@valeita
Copy link
Author

valeita commented Mar 26, 2019

It's very interesting, so the problem isn't the virtual machine. I don't have idea what is the problem.
I followed all your instruction, i tried to enforce to disable the signature check of a driver and tried to disable PatchGuard, but the service doesn't start (i'm only sure that the problem is the creating of the service). Have u tried it on Windows7 VM?

@valeita
Copy link
Author

valeita commented Mar 26, 2019

Anywhere, now i tried again all procedure follow all your step. i think that i didn't launched 1 of the three command line instrunctions to disable check of driver signature. Thanks very much for the gif.

@valeita
Copy link
Author

valeita commented Apr 8, 2019

Nothing. No idea why my virtual OS don't start the driver service.
I tried also this solution https://github.com/hfiref0x/UPGDSED.
Actually Win7 x64 doesn't work. If someone have the solution, please answer to this post.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants