Stealthy UM <-> KM communication system without creating any system threads, permanent hooks, driver objects, section objects or device objects
Stealthy UM <-> KM communication system without creating any system threads, permanent hooks, driver objects, section objects or device objects
Stealthy UM KM communication system without creating any system threads, permanent hooks, driver objects, section objects or device objects.
Process:
Limitations:
The driver is intended to be manually mapped by exploiting Intel's vulnerable network adapter diagnostic driver, iqvw64e.sys (or any other suitable vulnerable driver).
This was created for fun, I do not condone the use of this code in any program that violates the integrity of any online game, nor do I condone the use of this in any malicious software. This should only be used for learning purposes or to prevent custom software from being falsely detected as an illicit program.
Usage:
You have to modify the client to sleep until your target process is running (since it must be set up prior to any anti-cheat being active). Basic example of how main.cpp in the client should typically look:
int main() {
Client::Connect();
for (;;) {
Sleep(100);
if (YourTargetProcessIsRunning) {
break;
}
}
// Do stuff
Client::Disconnect();
}You can either call the functions in memory.h and process.h manually, or you can just create a KProcess object for easier use. KProcess features are as follows:
…No open issues yet, or sync has not completed.