Injectors
There are many injectors we use to insert .DLL file in game,
For those who dont know how to use injector and dll file here is the small tutorial
Tutorial:
1. Download an injector
2. Type process "iw3mp.exe"
3. Click browse and choose my .dll
4. click auto injection or you do it manually
5. ENJOY!
for some people, the hack won't work because of the missing dll file, and here is the solution
I see that a lot of people get the problem of missing msvcr100.dll, msvcr100d.dll, msvcp100.dll or d3dx9_*.dll errors. There are many ways to fix them but one of the most common is to Google the file name and just download the file from the internet from DLL sites. This can be dangerous as you might be downloading the wrong one and you could make your system unstable.
What does msvcr100d and msvcp100 mean?
MS = Microsoft
V = Visual
C = C or CP = C++
R = Runtime
100 = Version
D = Debug
How do I do it properly and safely?
Use Microsoft's official installers/redistributables to fix these problems.
Note about missing DLLs ending with a 'D'
This means whoever coded the application/hack didn't build it in Release mode meaning you'll have problems running it if you aren't a programmer. The only way (which I said not to do before) is to find the DLL manually on the internet and place it into the C
Windows\system32 folder. I am not responsible for anything that happens when you do this though. You can find some of them here.
Where can I find them?
To fix any msvcr100.dll or msvcp100.dll errors, you need to install the Microsoft Visual C++ 2010 SP1 Redistributable. Download the one that matches your computer's architecture (32-bit or 64-bit). Note that if you are running 64-bit, INSTALL BOTH.
Download: Microsoft Visual C++ 2010 SP1 Redistributable Package (x86) - Microsoft Download Center - Download Details (32-bit)
Download: Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) - Microsoft Download Center - Download Details (64-bit)
If you are getting mscvr110.dll or msvcp110.dll errors, install the Visual Studio C++ Redistributable 2012. You can find it here:
http://www.microsoft.com/en-us/downl....aspx?id=30679
Make sure to DELETE any msvcr100.dll or msvcr100d.dll files from your Combat Arms folder.
If you are asked to repair the installation, do it.
To fix any d3dx9_*.dll errors, use the DirectX Web Installer and make sure to install optional components.
Download: DirectX End-User Runtime - Microsoft Download Center - Download Details
How do I know if I'm running a 32-bit or 64-bit OS?
Please follow the instructions for your OS. (These were taken from Microsoft Support)
Windows Vista/7
1. Click Start
, type system in the Start Search box, and then click system in the Programs list.
2. When System Summary is selected in the navigation pane, the operating system is displayed as follows:
For those who dont know how to use injector and dll file here is the small tutorial
Tutorial:
1. Download an injector
2. Type process "iw3mp.exe"
3. Click browse and choose my .dll
4. click auto injection or you do it manually
5. ENJOY!
for some people, the hack won't work because of the missing dll file, and here is the solution
I see that a lot of people get the problem of missing msvcr100.dll, msvcr100d.dll, msvcp100.dll or d3dx9_*.dll errors. There are many ways to fix them but one of the most common is to Google the file name and just download the file from the internet from DLL sites. This can be dangerous as you might be downloading the wrong one and you could make your system unstable.
What does msvcr100d and msvcp100 mean?
MS = Microsoft
V = Visual
C = C or CP = C++
R = Runtime
100 = Version
D = Debug
How do I do it properly and safely?
Use Microsoft's official installers/redistributables to fix these problems.
Note about missing DLLs ending with a 'D'
This means whoever coded the application/hack didn't build it in Release mode meaning you'll have problems running it if you aren't a programmer. The only way (which I said not to do before) is to find the DLL manually on the internet and place it into the C
Windows\system32 folder. I am not responsible for anything that happens when you do this though. You can find some of them here.Where can I find them?
To fix any msvcr100.dll or msvcp100.dll errors, you need to install the Microsoft Visual C++ 2010 SP1 Redistributable. Download the one that matches your computer's architecture (32-bit or 64-bit). Note that if you are running 64-bit, INSTALL BOTH.
Download: Microsoft Visual C++ 2010 SP1 Redistributable Package (x86) - Microsoft Download Center - Download Details (32-bit)
Download: Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) - Microsoft Download Center - Download Details (64-bit)
If you are getting mscvr110.dll or msvcp110.dll errors, install the Visual Studio C++ Redistributable 2012. You can find it here:
http://www.microsoft.com/en-us/downl....aspx?id=30679
Make sure to DELETE any msvcr100.dll or msvcr100d.dll files from your Combat Arms folder.
If you are asked to repair the installation, do it.
To fix any d3dx9_*.dll errors, use the DirectX Web Installer and make sure to install optional components.
Download: DirectX End-User Runtime - Microsoft Download Center - Download Details
How do I know if I'm running a 32-bit or 64-bit OS?
Please follow the instructions for your OS. (These were taken from Microsoft Support)
Windows Vista/7
1. Click Start
, type system in the Start Search box, and then click system in the Programs list.2. When System Summary is selected in the navigation pane, the operating system is displayed as follows:
- For a 64-bit version operating system: 64-bit Operating System appears for the System type under System.
- For a 32-bit version operating system: 32-bit Operating System appears for the System type under System.
Windows XP
1. Click Start, and then click Run.
2. Type sysdm.cpl, and then click OK.
3. Click the General tab. The operating system is displayed as follows:
1. Click Start, and then click Run.
2. Type sysdm.cpl, and then click OK.
3. Click the General tab. The operating system is displayed as follows:
- For a 64-bit version operating system: Windows XP Professional x64 Edition Version < Year> appears under System.
- For a 32-bit version operating system: Windows XP Professional Version <Year> appears under System.
Note <Year> is a placeholder for a year.
I'm a coder, how can I prevent this from happening to people when they use my hacks?
If you are a coder and use Visual Studio 2010 or Visual C++ 2010 Express, you should tell users to install the redistributable before using the hack. You can also 'statically link' the DLLs required so the user doesn't need to install anything at all! It basically embeds the data required inside your hack.
EDIT - If you are using Visual Studio 2012, make sure to change the Platform Toolkit via the Project Properties to Visual Studio 2012 (v100) otherwise it will NOT work for users on Windows XP! Click here for an image.
How to statically link the DLLs:
1. In Visual Studio, right-click on your project and click Properties.
2. Change the Configuration to Release (at the top).
3. Click on Configuration Properties > C/C++ > Code Generation
4. Change the Runtime Library option to Multi-threaded (/MT)
5. Click OK and rebuild your project (right-click on your project and click Rebuild).
The new copy of your hack should be in your project's Release folder.
Why would I want to change the configuration from Debug to Release?
Firstly, most computers do not have the Debug version of the DLL (msvcr100d.dll). It's recommended that you release all your hacks in Release mode (make sense right?). It will also remove some safety stuff that's only required during testing and will generally improve the speed/performance of your hack because the compiler often optimises the code more. The same thing even applies to applications coded in .NET, the only difference is you can't statically link anything.
Injectors
- PerX Injector -
Rullez Dual Language
Extreme Injector
Extreme Injector v2.1
A powerful and advanced injector in a simple GUI!
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, Thread Hijacking and Manual Map)
- Drag and drop support
- 64-bit injection support.
How to use:
- Download and extract the attachment
- Run Extreme Injector v2 by master131.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.
- (Note) You do not need to use the "Scramble DLL" button under Tools unless you want to use a scrambled DLL with a seperate injector. The injector will automatically scramble the file before it is injected into the game.
- (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.
- Thread Hijacking - This was the "Alt" injection techinique seen in the previous version. It is pretty stable 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. This injection technique may have problems with hacks that are packed with a packer so try another method if this doesn't work.
Please explain the Scramble Options!
If you've used DLL Scrambler, you're probably familiar with these options.
- Scramble DLL - Tick this to enable/disable DLL Scrambling completely
- Scramble Header - This will scramble the area around the start of the file which should not impact the DLL at all
- Remove Debug Data - This will remove a string in the DLL (as well as 'Debug Data') which Anti-Cheat vendors *could* use as a signature.
- Append Random Data - This will add random data to the end of the file.
- Shift Section Code - This will shift or move some of the assembly code (and other data in the DLL) using a random offset. This is good if an anti-cheat tries to search for a specific signature at a specific offset.
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.
About the new 64-bit injection:
That's right, this new version of Extreme Injector supports 64-bit DLLs and 64-bit processes. On a 64-bit computer, the injector runs as a 64-bit process and on a 32-bit computer, it runs as a 32-bit process. That means you can inject 64-bit hacks into 64-bit processes (don't worry, you can still inject into 32-bit processes on a 64-bit OS). There's a problem though. There are probably zero 64-bit hacks out there and there are hardly any 64-bit games. This is just a feature I decided to add for the future. For example, the next version of the Frostbite engine (used by Battlefield) will force users to have a 64-bit OS. This may be useful if 64-bit hacks were to appear.
Known bugs/limitations:
- Thread Hijacking is not supported at all on XP 64-bit.
- 64-bit injection only supports Standard injection (if you choose another injection technique, it will automatically use the Standard one).
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 using another injection method, some do not work with all hacks.
Requirements:
.NET Framework 3.5
What's new?
I'm a coder, how can I prevent this from happening to people when they use my hacks?
If you are a coder and use Visual Studio 2010 or Visual C++ 2010 Express, you should tell users to install the redistributable before using the hack. You can also 'statically link' the DLLs required so the user doesn't need to install anything at all! It basically embeds the data required inside your hack.
EDIT - If you are using Visual Studio 2012, make sure to change the Platform Toolkit via the Project Properties to Visual Studio 2012 (v100) otherwise it will NOT work for users on Windows XP! Click here for an image.
How to statically link the DLLs:
1. In Visual Studio, right-click on your project and click Properties.
2. Change the Configuration to Release (at the top).
3. Click on Configuration Properties > C/C++ > Code Generation
4. Change the Runtime Library option to Multi-threaded (/MT)
5. Click OK and rebuild your project (right-click on your project and click Rebuild).
The new copy of your hack should be in your project's Release folder.
Why would I want to change the configuration from Debug to Release?
Firstly, most computers do not have the Debug version of the DLL (msvcr100d.dll). It's recommended that you release all your hacks in Release mode (make sense right?). It will also remove some safety stuff that's only required during testing and will generally improve the speed/performance of your hack because the compiler often optimises the code more. The same thing even applies to applications coded in .NET, the only difference is you can't statically link anything.
Injectors
- PerX Injector -
Rullez Dual Language
Extreme Injector
Extreme Injector v2.1
A powerful and advanced injector in a simple GUI!
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, Thread Hijacking and Manual Map)
- Drag and drop support
- 64-bit injection support.
How to use:
- Download and extract the attachment
- Run Extreme Injector v2 by master131.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.
- (Note) You do not need to use the "Scramble DLL" button under Tools unless you want to use a scrambled DLL with a seperate injector. The injector will automatically scramble the file before it is injected into the game.
- (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.
- Thread Hijacking - This was the "Alt" injection techinique seen in the previous version. It is pretty stable 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. This injection technique may have problems with hacks that are packed with a packer so try another method if this doesn't work.
Please explain the Scramble Options!
If you've used DLL Scrambler, you're probably familiar with these options.
- Scramble DLL - Tick this to enable/disable DLL Scrambling completely
- Scramble Header - This will scramble the area around the start of the file which should not impact the DLL at all
- Remove Debug Data - This will remove a string in the DLL (as well as 'Debug Data') which Anti-Cheat vendors *could* use as a signature.
- Append Random Data - This will add random data to the end of the file.
- Shift Section Code - This will shift or move some of the assembly code (and other data in the DLL) using a random offset. This is good if an anti-cheat tries to search for a specific signature at a specific offset.
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.
About the new 64-bit injection:
That's right, this new version of Extreme Injector supports 64-bit DLLs and 64-bit processes. On a 64-bit computer, the injector runs as a 64-bit process and on a 32-bit computer, it runs as a 32-bit process. That means you can inject 64-bit hacks into 64-bit processes (don't worry, you can still inject into 32-bit processes on a 64-bit OS). There's a problem though. There are probably zero 64-bit hacks out there and there are hardly any 64-bit games. This is just a feature I decided to add for the future. For example, the next version of the Frostbite engine (used by Battlefield) will force users to have a 64-bit OS. This may be useful if 64-bit hacks were to appear.
Known bugs/limitations:
- Thread Hijacking is not supported at all on XP 64-bit.
- 64-bit injection only supports Standard injection (if you choose another injection technique, it will automatically use the Standard one).
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 using another injection method, some do not work with all hacks.
Requirements:
.NET Framework 3.5
What's new?
Code:
Changes since version 2.1 (20th October 2012):
- Fixed drag and drop to work when its run as admin
Changes since version 2.0 (19th October 2012):
- Rewrite from scratch
- Added 2 new injection techniques
- Added 64-bit DLL injection support
- Added 64-bit process support
- Added post-inject options for extra stealth
- Added drag and drop support
- Settings are now stored in an XML file. (requested via PM)
- Improved DLL verification
- Renamed some scrambling features
- Tweaked GUI
- Better injection result reporting
- Stealth Inject now works with Combat Arms again
hope it helps
0 comments: