Helpc# dll Not Running Code After Inject

Posts 1–10 of 10 · Page 1 of 1

c# dll Not Running Code After Inject

I have been making external cheats for a while but I have never tested them online because I don't want to waste $10 on an account jest getting vacced.

I was almost ready to test my external online.
Then I read a post on MPGH about vac detects open handles (for RPM and WPM(I don't use)) I figure that if I modify my c# external into a dll and inject it into something that vac commonly sees with an open handle like "game booster" and such.

That it will be harder to detect (Please correct me if that line of thinking is incorrect).

So the overall plan is to:

1. Modify my external .exe cheat into a dll (Done).
2. Inject it into a process (Done. Injector works)
3. Modify game memory from the program I injected into such as gamebooster

The issue is after injecting the c# dll into the process e.g. (game booster) the code in the c# dll does not run.

The injector works for sure because I injected a simple c++ message box dll into game booster and the code ran.

After googling around I learned that I need to use a c++ "wrapper" to run the c# dlls after they are injected but I can't seem to find any more info on how to actually do it.

So in final I have 2 questions

1. Assuming no C+P, if I leave my cheat as external e.g. ( Standalone .exe file) and use a heavily modified public memory library would it be detected right away?

or

2. How can I make the c# dll's code run after injection with a c++ wrapper.

Sorry for the long post, but after I'm done coding my cheat I might just put it on mpgh because of all the resources that have helped me on here. Im very thankful to have learned so much over the past few months.

Originally Posted by Foxxy Boxxy

public memory libraries dont get your cheat detected, i personally use procmem for my externals

Thanks for replying

Are you sure? I read that using any public code spinets above a certain size can get you cheat detected if unmodified. I use a personal modified version of VAmemory from 2010 (While reading about memory editing before I knew anything. People recommended it on old forums posts. ) with everything I don't need striped out and modified.

Do you have anymore tips on staying undetected with an external .exe cheat?

Won't vac just see my open handle for (RPM) from my unrecognized program then scan my cheat and get detected?

Originally Posted by Foxxy Boxxy

no it wont, I've personally been using procmem for over a year in my private cheat and i have yet to be banned from it

Just because you inject your Managed .dll into a managed process dosen't mean it will run.
You'll have to create a thread and run it, or simply run it from the thread you inject into. It won't start automaticly.

+ You don't need a c++ wrapper, you could do a very simple runPE.

Thanks so much for answering my question. But I have looked all over and can't find any examples of runPE applicable to this context. Do you think you could give a short example?

Originally Posted by Foxxy Boxxy

Thanks so much for answering my question. But I have looked all over and can't find any examples of runPE applicable to this context. Do you think you could give a short example?

This should give you a head start.
http://www.adlice.com/runpe-hide-cod...legit-process/ that code is in c++ how ever, you can do it the same way in C# / VB.

Or you could just earch for a source code if you want to get going fast. There are some sources in VB.net you could just translate them to c# your self or use http://converter.telerik.com/ to convert the code for you.

Thanks again for the reply Carlsson. I found some suase for a c# runPE application: hastebin com/oyeyuhozuy.cs

Does this look like a good one? I have downloaded and fixed a bit of it but, instead of it running my cheat inside of the "skin" of another .exe it just opens hundreds suspended target processes (The exe I wanted to inject into). Do you have any ideas why this happens?