Rullez Injector Simple

[Rullez]

My New Injector// Simple // Undetected



Made In C++

1 - Open As Administrator
2 - Select You DLL In Browse// Problem Use Remove/Clear List
3 - Select Automátic Inject
4 - Select Closed After Inject
5 - Open Vindictus



Vírus Total
Jotti

Crédits @Rullez
Aprovee

@Nico
@Dave84311

[Meta]

Nice, you took one of the C++ tutorial injector source codes, compiled it, and called it your own program. Wasn't hard of you considering that anyone can compile the source code and make a simple GUI. At least with MetaJect I overhauled a whole lot of code to make it more user-friendly. Just my opinion, I really don't see why the community needs more injectors. CrX's window injector was the best. But it didn't support multi dll injection which is why it became a hassle to use.

Considering how many injectors look just like that, (look at Supremeject for example), I don't see why you uploaded this. You have changed nothing from the original source code. The only difference is that you just made the GUI blue.

Chances are you probably didn't add error checking. What if I entered "Vindictus.exe" rather than just "Vindictus"? Does it automatically "load" the last saved dlls?

I'll end my little tangent but please remember this isn't exactly a contribution because it's been done hundreds of times. At least personalize it with something that all 100+ injectors don't already have.

[maddoggy00]

Approved @Rullez
Just as a heads up, this doesn't seem to work if you're running on a x64 OS. And automatic injection does not work on x86, at least for Vindictus.

Considering how many injectors look just like that, (look at Supremeject for example), I don't see why you uploaded this. You have changed nothing from the original source code. The only difference is that you just made the GUI blue.

Chances are you probably didn't add error checking. What if I entered "Vindictus.exe" rather than just "Vindictus"? Does it automatically "load" the last saved dlls?

I don't think he added in much beyond the basics. Either way there's no public .dll for Vindi anyway, so no reason to get antsy.

[xCr3fgt]

what that ?