Today I tested a DLL with some Luastuff. I want this DLL to be injectable and ejectable "on the fly". Injection works fine. But I tested like 30min why 'Winject 1.7' refuseses to eject my DLL. First I thought there must be a mistake in my DLL ... like something is not cleaned up correctly ... but then I noticed something:
Winject always refuses to eject ANY DLL after the Login.
To be 100% sure I created a simple empty DLL like this ...
PHP Code:
#include <Windows.h>
bool attached = false;
BOOL WINAPI DllMain(HINSTANCE hDLL,DWORD Reason,LPVOID Reserved)
{
switch(Reason)
{
case DLL_PROCESS_ATTACH:
attached = true;
break;
case DLL_PROCESS_DETACH:
attached = false;
break;
}
return TRUE;
}
I tested another DLL -In-/Ejector called 'RemoteDLL' by Nagareshwar Y Talekar and it worked. But I trust 'Winject' much more because its obviously made more professional.
So my Question is:
Any ideas why Winject refuses to eject any DLL after the login? ...srsly that pisses me off
I have attached the two DLL Injectors and the empty DLL for testing purposes.
This stuff may trigger ur AV, so noobs stfu!







