[Help] Linking C++ DLL and Visual Basic Executable Together

Linking C++ DLL and Visual Basic Executable Together

Title says half.
Okay, im working for a hack and I do not want it to be shared or leeched.
I wanted to make the executable to link with the C++ DLL when it is injected.
I only wanted the dll to be injected by MY executable or loader.
Is it a way to make this work?

Originally Posted by buxkaizhe

Title says half.
Okay, im working for a hack and I do not want it to be shared or leeched.
I wanted to make the executable to link with the C++ DLL when it is injected.
I only wanted the dll to be injected by MY executable or loader.
Is it a way to make this work?

Embed the DLL as a resource

Originally Posted by user590177

Embed the DLL as a resource

I dont want it to be injected by other injectors. I only wanted it to be injected from my Loader / Injector. Adding it at resources does not seems to be the way to solve this problem.

Originally Posted by buxkaizhe

I dont want it to be injected by other injectors. I only wanted it to be injected from my Loader / Injector. Adding it at resources does not seems to be the way to solve this problem.

Make the loader download the hack and directly inject it then.

Originally Posted by user590177

Make the loader download the hack and directly inject it then.

It's still possible to catch the file, same when it's saved as a resource.
- OT: It's just an idea, not sure if it will work or not, but make on the injection of the Dll to check if your injector process is opened or not.

Originally Posted by Mayion

It's still possible to catch the file, same when it's saved as a resource.
- OT: It's just an idea, not sure if it will work or not, but make on the injection of the Dll to check if your injector process is opened or not.

You can add additional security checks, plus encrypt the DLL.

Originally Posted by user590177

You can add additional security checks, plus encrypt the DLL.

That's what he's asking for. lol
Also, by encrypting the dll you're not stopping others from extracting it. It's like saying encrypting my files will stop hackers from accessing them

Originally Posted by Mayion

That's what he's asking for. lol
Also, by encrypting the dll you're not stopping others from extracting it. It's like saying encrypting my files will stop hackers from accessing them

Well yes, tbh there's no unbreakable way to protect something. Everything can be cracked.
I am sure most of the people wouldn't even understand how encryption works (as they are probably kids who just want to hack or leech other's work) and therefore wouldn't even bother to crack the encryption. So encryption adds a huge protection to the loader.
OT: A safe way to do this is by using some asymmetric encryption method.

Yes, you can. What is the problem? @Mayion what you said have not any sense.
You must use DllImport actually to call a native function in vb.net.
Anyway, P/Invoke calls LoadLibrary on native dll.

Originally Posted by Raydenman

Yes, you can. What is the problem? @Mayion what you said have not any sense.

Which part are you referring to?

Originally Posted by Mayion

Which part are you referring to?

Why should you ENCRYPT?

Um. Now I have some tips. My friend told me that is is some communication between the dll and vb application. Is there any way to make vb.net send something to a dll? And encrypting does not work on my loader as people can still inject them into the game easily if they got the dll file.

Originally Posted by buxkaizhe

My friend told me that is is some communication between the dll and vb application.

O really?

Originally Posted by buxkaizhe

Is there any way to make vb.net send something to a dll?

Send what?

Watch my first reply on this topic.

Originally Posted by buxkaizhe

Um. Now I have some tips. My friend told me that is is some communication between the dll and vb application. Is there any way to make vb.net send something to a dll? And encrypting does not work on my loader as people can still inject them into the game easily if they got the dll file.

As I've said, on injection have the Dll to check if your loader process is on or not. - In the code of your dll itself.
> If loader process = true, execute the rest of the code, if not, show up a message saying injection failed.

Originally Posted by Mayion

As I've said, on injection have the Dll to check if your loader process is on or not. - In the code of your dll itself.
> If loader process = true, execute the rest of the code, if not, show up a message saying injection failed.

O really? pt.2
This was already served, but I still can't understand why you shouldn't do it already from vb.net ...

HelpLinking C++ DLL and Visual Basic Executable Together

Post a Reply

Similar Threads

Tags for this Thread