Memory Hacking Software

I have a suggestion regarding the DLL injector.

Say the following situation:

You're developing a DLL that will get injected into a target process, but you haven't written the injector itself yet... so you use the MHS DLL Injector.
What I really like about MHS is that after a target closes, it will wait for it to re-open.. it makes life easier.

But now the problem/suggestion:
After injecting a DLL and closing the target application you make changes to the DLL and re-build it. But MHS still has the DLL opened so the compiler can't write to it anymore.

So is it possible to release the DLL after the target process died?

Edit:
Everything does get released when I click 'uninject selected DLL' ... So I guess that will do for a (hopefully temp) solution.

Unrelated question:
I remember that you were working on an aimbot tutorial a while ago Spiro, but I haven't seen it pop up somewhere.. are you still working on it or simply too busy?

Modifications to MHS are unlikely.

And I have been more than busy. The tutorial will have to wait.


L. Spiro

Have you considered letting someone else(or multiple people) continue development on MHS?

Of course it is at a great state.. but for maintenance to fix things like this.

I have, and the source may be freely available in a year or so.


L. Spiro

@L:
That would be great, and fair for those who purchased it.

@trouble:
Writing a own injector really isn't that hard. (unless you want reflective mapping in it )

I know felheart. But in the begin stage I like to use the MHS' injector, and I noticed this 'problem'

In computer programming, DLL injection is a technique used to run code within the address space of another process by forcing it to load a dynamic-link library. DLL injection is often used by third-party developers to influence the behavior of a program in a way its authors did not anticipate or intend. For example, the injected code could trap system function calls, or read the contents of password textboxes, which cannot be done the usual way. This is mainly done in game hacking.

Read the full article here: http://en.wikipedia.org/wiki/DLL_injection


L. Spiro

denialmark wrote:In computer programming, DLL injection is a technique used to run code within the address space of another process by forcing it to load a dynamic-link library. DLL injection is often used by third-party developers to influence the behavior of a program in a way its authors did not anticipate or intend. For example, the injected code could trap system function calls, or read the contents of password textboxes, which cannot be done the usual way. This is mainly done in game hacking.

Good job with the copy and paste from wikipedia, next time just post the link... There's no need for you to try sounding smarter than you actually are, especially when you provide no help to the solution. What a waste, and look you made me waste a post and some time as well.


@troublesh00ter: If you want I can upload my dll injector. It has some nice features such as the usual Watch for Process plus some new ones I found useful.

Ignore it. It is a bot of some kind but I want to study its behavior to see its pattern and objective.
Everything it has posted has been a copy-and-paste from somewhere, including a question that was almost on-topic.


L. Spiro