Yo.OG. Source from Scripter4Ever, however I've updated it to VB.Net standards and cleaned it up.This, is what either of LoadLibrary entry points look like before execution of the code:This is what it looks like after:The first statement of LoadLibrary was just replaced by a return statement, causing any dll injector using LoadLibrary to fail (because when LoadLibrary is being called, it just returns without loading the actual dll into the process).Hope you guys enjoy, I wouldn't rely on this too much though as it'd be fairly easy to reverse, but none the less it gets the concept across.
ok