Xed Injector - Manual Map/LdrLoadDllStub/Thread Hijacking/Cloaking
Xed Injector
An advanced injector with fresh code in order to be sure there will be no interruptions while attempting to use your cheat.
Screenshots:
Injection methods:
- Load Library (Simple, safe injection, but detected)
- Manual Map (Not simple manual map, but instead it maps an actual loader for your image, making sure it will stay undetected)
- LdrLoadDllStub (One level deeper into LoadLibrary, this is a re-written version of the exported function LdrLoadDllStub)
- Thread Hijacking (This is completely undetected for the moment and can be used in a vast majority of applications)
Other options:
- Spoof PE Header (Replaces your image's PE header with one from the kernel32 module, thus reducing detection rates)
- Cloak module (Makes your image invisible in the module list)
Upcoming:
In the case that this release won't be a complete failure, I have the following features in my head for the next version:
- I will make this ugly GUI into a more compact and easy to use one
- Make the process list easier to navigate (and maybe include the icons)
- Add double thread hijacking and LdrpLoadDllStub
- Include console versions so you can use them instead or use them with your own programs
- Automatic x64 architecture process detection (didn't have time to include it in this version, was in a bit of a hurry)
- View what caused the error
Scans:
These files are virtualized with VMProtect, thus the detection rates will probably be a bit high. Also, cannot post VT scan because it is currently broken.
https://virusscan.jotti.org/en-US/fi...job/0tjmgtoe5gⓘ
https://metadefender.com/#!/results/...gular/analysisⓘ
If you have any issues with this or any other questions in general, feel free to ask. Also, if the GUI is broken in any way, post it here and I'll fix it asap. I haven't really payed much attention to it, it's just a very simple VB code. Will probably switch to something like Delphi or just use MFC for the GUI later on.
An advanced injector with fresh code in order to be sure there will be no interruptions while attempting to use your cheat.
Screenshots:
Injection methods:
- Load Library (Simple, safe injection, but detected)
- Manual Map (Not simple manual map, but instead it maps an actual loader for your image, making sure it will stay undetected)
- LdrLoadDllStub (One level deeper into LoadLibrary, this is a re-written version of the exported function LdrLoadDllStub)
- Thread Hijacking (This is completely undetected for the moment and can be used in a vast majority of applications)
Other options:
- Spoof PE Header (Replaces your image's PE header with one from the kernel32 module, thus reducing detection rates)
- Cloak module (Makes your image invisible in the module list)
Upcoming:
In the case that this release won't be a complete failure, I have the following features in my head for the next version:
- I will make this ugly GUI into a more compact and easy to use one
- Make the process list easier to navigate (and maybe include the icons)
- Add double thread hijacking and LdrpLoadDllStub
- Include console versions so you can use them instead or use them with your own programs
- Automatic x64 architecture process detection (didn't have time to include it in this version, was in a bit of a hurry)
- View what caused the error
Scans:
These files are virtualized with VMProtect, thus the detection rates will probably be a bit high. Also, cannot post VT scan because it is currently broken.
https://virusscan.jotti.org/en-US/fi...job/0tjmgtoe5gⓘ
https://metadefender.com/#!/results/...gular/analysisⓘ
If you have any issues with this or any other questions in general, feel free to ask. Also, if the GUI is broken in any way, post it here and I'll fix it asap. I haven't really payed much attention to it, it's just a very simple VB code. Will probably switch to something like Delphi or just use MFC for the GUI later on.
Originally Posted by Ahl
