Remote inject module from byte array

[ntKid]

Here is another way to "map" a module into a target process.

This method will not try to replicate "LoadLibrary" it will change some procedures of the function itself and by doing this your stream is initialized normally by the system and there is no stress with floating point or crt issues.

/*
CONCEPT BASED ON ( nologin )
> I DIDNT MANAGE TO FORCE NTOPENFILE TO RETURN A VALID FILEHANDLE OF A NON EXISTANT FILE...
ONLY WAY I FIGURE OUT IS BY NOT GOING AGAINST NATURE AND POINTING IT TO A DUMMY MODULE ON HD.

CREDITS:
> nologin( Concept )
> Azorbix( Detours )
> ntKid( Coder )
*/

[ᵁᴻᴷᴺᴼᵂᴻ]

Re: Remote inject module from byte array

thanks,
recently did something similar too.

[mencore]

Re: Remote inject module from byte array

thanks,
recently did something similar too.

Rifk, if this shit is confusing, your stuff is that to the max. Unless you've done something lately I didn't know about, if not your manual mapping stuff is awesome AND CONFUSING AS FUCK [noparse] :D [/n??rse]

[ᵁᴻᴷᴺᴼᵂᴻ]

Re: Remote inject module from byte array

Rifk, if this shit is confusing, your stuff is that to the max. Unless you've done something lately I didn't know about, if not your manual mapping stuff is awesome AND CONFUSING AS FUCK :D

yup it's more recent than "manual map" dll_map class and nothing is posted 'yet'.
it was made for allowing me to remove the 'injector/downloader' second module that the client originally injected in the target to download fix and resume the hack,
now the client download write fix and resume shit on it's own using a similar but different method than that(and yes i plan to release 'who knows when' but will).