Extreme Injector v3.2

[[MPGH]master131]

Extreme Injector v3.2

The latest version can be found here.

A powerful and advanced injector in a simple GUI! If you're wondering, this was coded in C#. This is a rewrite of the widely known v2.1 which can be found here.







Features:
- Colourful and customizable GUI
- Process List
- Multi-DLL injection (with options to enable/disable DLLs to inject)
- Auto-Inject
- Stealth Inject
- Close on inject
- DLL Scrambling (scrambles DLLs on injection to make hacks harder to detect and make detected hacks work again)
- 'Un-inject' DLLs
- Mutiple injection methods (Standard, LdrLoadDll Stub, LdrpLoadDll Stub, Thread Hijacking and Manual Map)
- Drag and drop support
- 64-bit injection support
- Automatic Visual C++ depedency installer

How to use:
- Download and extract the attachment
- Run Extreme Injector v3.exe
- (optional) Click Settings and then Start in Secure Mode to avoid Anti-Cheat detection of the injector itself.
- Type in a process name into the box (including the extension). If you want to target a specific process or select by window name, use the Select button.
- (Note) If you are injecting into Combat Arms, make sure to type in Engine.exe
- Add the DLLs you want by clicking on the Add DLL button. You can also drag and drop them into the DLL list.
- You can disable/enable which DLLs to inject so you can keep your favourite DLLs without needing to find them each time.
- Go into Settings and customise the settings to your liking. Everything should be straight forward (do not mess around with Advanced settings unless you know what you are doing).
- (Note) If you are injecting into Combat Arms, make sure to tick Auto-Inject and start the game.
- Click Inject and enjoy! (or wait for the process to start and let it auto-inject if you ticked auto-inject)

Please explain the Injection Methods!
This version of the injector introduces 2 new injection techniques.
- Standard - This is the injection technique used in nearly every injector out there. It uses CreateRemoteThread and LoadLibrary and is the most reliable injection technique.
- LdrLoadDll Stub - This is similar to the Standard injection technique except it goes 1 level deeper into LoadLibrary.
- LdrpLoadDll Stub - This goes even another level deeper into LdrLoadDll. It may crash or cause errors on OSes newer than Windows 8.1 as it can change.
- Thread Hijacking - This is a pretty stable method of injection that takes over already executing code to inject your DLL and is not used by many injectors.
- Manual Map - This is the most secure injection technique. So secure that even Windows won't even know about the injected DLL. It may not work properly on OSes newer than Windows 8.1, you will be told what to do by the injector in that case.

Please explain the Scramble Options!
With the new version of Extreme Injector v3, there are way too many options to explain so I've created handy presets to make things easier:
None - As the name implies, this means that DLL scrambling is disabled completely.
Basic - This applies basic scrambling that should work with most DLLs.
Standard - This applies even more scrambling options that should work with most DLLs.
Extreme - Applies all scrambling options (the best/strongest preset) that could break some DLLs but should work with most.

Please explain the Post-Inject Options!
These post-inject techniques are often seen within hacks to try prevent detection from anti-cheats but this injector can do it externally if the hack doesn't do it already.
- Erase PE - This erases the PE headers at the start of the injected DLL, making it hard for anti-cheats to identify that a DLL exists at a specific location.
- Hide Module - This hides the DLL from the process' module list so if an anti-cheat were to search through a process' module list, it would not appear.

Warning: Most modern anti-cheats these days can still easily detect DLLs even with these options enabled. The most secure method would be using manual map.

Known bugs/limitations:
- Thread Hijacking is not supported at all on XP 64-bit.
- LdrpLoadDll has only been tested on XP, Vista, 7, 8 and 8.1. It will probably not work on anything newer than that.
- "Create new entrypoint" under scrambling advanced options does not support 64-bit DLLs.

When using 'Start in Secure Mode'....
If your anti-virus detects a threat/virus when you click on it, please ignore it or temporarily disable your anti-virus, it's a false positive. I would never infect any users with anything. Note that you should NOT add an exclusion to the Temp folder as any REAL viruses that emerge there might get through.

Injection failed...?
Try another injection method and see what happens. Feel free to take a screenshot or copy and paste the error message here so I can look into it. Make sure to mention what OS you are running.

What's the Visual C++ depedency installer?
If Extreme Injector detects that a hack you are adding requires MSVCR<version>.dll or MSVCP<version>.dll and you do not have it installed, it will offer to automatically download the correct version (x86 or x64) from the Microsoft website and install it for you. If it detects the hack you are adding requires MSVCR<version>D.dll or MSVCP<version>D.dll, it will automatically download the correct version (x86 ox x64) and save it to the correct folder (C:\Windows\system32 or C:\Windows\SysWOW64). This is all so people don't complain about non-working hacks and don't end up downloading and saving files to the wrong place.



Requirements:
.NET Framework 4

What's new?

Changes since version 3.2 (9th June 2014):
- Fixed bug where auto-inject did not seem to work
- Addressed possible crashing from messages failing to display during injection

Changes since version 3.1 (3rd June 2014):
- Fixed bug where a message box would appear randomly if a Visual C++ dependency was missing (leftover from testing code)
- Fixed bug where selecting "No" from the prompt under Advanced in Injection Method would untick the wrong box
- Injector now displays a message box saying that injection was successful

Changes since version 3.0 (31st May 2014):
- Complete rewrite from scratch (same and familiar look from previous versions)
- All injection techniques are now 100% compatible with 64-bit DLLs
- Drag-and-drop fixed when run as administrator on newer OSes
- Automatically elevates without asking if it knows you have administrator rights
- Better scaling on displays with a DPI higher than 96
- Added a Visual C++ Dependency Installer
- Manual map now supports DLLs that use SEH to work (better packer support, eg. Themida, Enigma, etc)
- New injection technique: LdrpLoadDll
- Better exception/error reporting
- New scrambling engine, more scrambling methods
- Removed "Append Random Data" as it just wasted disk space and is ineffective
- Improved detection of different OS versions
- Dynamic assembly code generation (powered by AsmJit)
- Seperate process, thread and window manager, does not rely on .NET Process class anymore
- "Start in Secure Mode" creates an even more "secure" instance of Extreme Injector

Credits:
DarthTon - Better manual map code (originally coded in C++, ported to C# by me, licensed under MIT).
Darawk - Thread hijacking code concept.

Virus Scans:
https://www.virustotal.com/en/file/1...cab4/analysis/
https://virusscan.jotti.org/en/scanre...03256c3b6c498d

At the time of posting this thread, VirusTotal reported (3/51) and Jotti reported (2/22). This is expected to increase as AV vendors flag this injector as a hack tool. The injector itself is not malicious, please ignore these warnings.

If your anti-virus detects this as a virus, ignore it or add an exclusion. It is not a virus, you can run it under a sandbox and log every single thing it does, it's harmless.

[Fєηix]

Good Work

[6ixth]

Great JOb man, 3.2 fixed error?

[giakoumis]

Thank for your hard work! Master I have a suggestion for you. In the next release please add a checkbox in settings to start always in safe mode or not instead of starting it from settings and then have to close the not safe version. There are people out there who want to start the injector always in safe mode. Thanks

[Neox.]

Good Job

[babydo]

Any idea how to fix the 'ntdll.dll' error?

[Sbottering]

THANKS YOU BABY

[Unbalanced]

Nice update man! Extreme Injector = Best injector

[[MPGH]master131]

Any idea how to fix the 'ntdll.dll' error?

Can you screenshot or type the full message? Also, what OS are you running.

[slimcharles]

Does this injector have any interaction with VAC?

[[MPGH]master131]

Does this injector have any interaction with VAC?

Why would it communicate with VAC?

Also, found a bug which uses one entire core from waiting for a process to close (woops), will fix in the next version.

[slimcharles]

VAC is very finicky with any modification to DLL's or any odd processes.

I am using the injector for Battlefield 3, but I run Steam games (which use VAC) at the same time.

[Ineedbf3hacks]

Everytime I run it. It disappeared. Starting to think this is a rat.

[[MPGH]master131]

Everytime I run it. It disappeared. Starting to think this is a rat.

You probably ticked auto-inject and have the target process still open. Just delete "settings.xml" and start the injector again. The notion of people even suggesting that this is a RAT makes me

Also, currently working on an experimental scrambling setting that shifts the location of a DLL's contents in memory (basically shifting all the section virtual addresses). This should help to prevent detection on anti-cheats that hard-code memory offsets and don't read the DLLs from disk.

Only problem is that this could easily make DLLs stop working so I might make an Ultra preset or something.