Code Water Marking

Well it seems some "Coders" are a little paranoid about there compiled dll's and exe's getting hex edited, I have a simple solution which will catch out the the people doing this. Its code watermarking, An encrypted byte array with your "Tag" which at entry point gets put into EAX register, For reading the watermarking its just a mater of loading the dll and reading the value of EAX to determine who this originally came from. I can code up something for proof of concept but it would be in delphi, Im sure for most C++'ers just explaining how to go about would do. if you have other ideas please feel free to share them in this topic, Luckily for me, from what I have seen I am the only one who codes hacks for CA in Delphi, which means its pretty easy to tell if my stuff gets ripped.

you lost me at "Well it seems some "Coders""

lol I semi understand the concept ;p

Never heard of Code Watermaking only like Picture...

Go Ahead bro

Meh I just have people who use my hacks added to my RAT server so I can check if they are leeching my hack.

Originally Posted by NOOB

Meh I just have people who use my hacks added to my RAT server so I can check if they are leeching my hack.

And your loader ? hehehe

If you read some topics here on this forum some people are saying they are packing/protecting there apps and dll's so that noobs don't steal there shit. And yes I know the crazy theory about packing a dll makes it "Undetected" which is not true(Using a protector could undetect the dll due to code modifications). I just wanted to suggest an idea for tagging your apps and dll's so you know if someone has ripped your shit. If the Noob is smart enough to decrypt the "tag" which would be an array of bytes, then they are smart enough to make there own hacks and wouldn't bother ripping yours.

//Edit

Another way to tag your shit and make unworkable if messed with is the the hack address's and byte patches, an example would be say you have an array of bytes $C0,$75,$90 then you took your name "Departure" for each character of your name you could multiple, add, subtract, modulas it with each of the bytes in your array. This would give you an encrypted array which your name is the key to decrypt it, then when writting these bytes to memory you decrypt by passing your name("Tag") as the key. this will do 2 jobs, 1st if someone ripps your addresses it will never work unless they decrypted it, and second if you read the encrypted byte array the only key that will decrypt it is your "Tag" which means you have tagged your dll in such away that unless the noob works out the key and the encryption there is no way for them to steal your shit, and if they did it wouldn't work.

Originally Posted by Departure

If you read some topics here on this forum some people are saying they are packing/protecting there apps and dll's so that noobs don't steal there shit. And yes I know the crazy theory about packing a dll makes it "Undetected" which is not true(Using a protector could undetect the dll due to code modifications). I just wanted to suggest an idea for tagging your apps and dll's so you know if someone has ripped your shit. If the Noob is smart enough to decrypt the "tag" which would be an array of bytes, then they are smart enough to make there own hacks and wouldn't bother ripping yours.

well said

Pretty obvious if someone leeches a hack, and the average hack user wouldn't know to check the tag, they just want a hack to use. By packing or encrypting you stop them from changing text on the menu so they can't leech it in the first place. And anyone can make a hack now, no leeching necessary.

My hacks are encrypted in the first place

+ My GUI is completely made in photoshop.
No way they can hex edit my shit

Originally Posted by flameswor10

My hacks are encrypted in the first place

+ My GUI is completely made in photoshop.
No way they can hex edit my shit

Apparently you can edit the image bytes and remove the image completely

Originally Posted by markoj

Apparently you can edit the image bytes and remove the image completely

OFcourse, That is possible. But that'd mean hex editing out 3 byte arrays, because I use 3 set of bytes to make my menu GUI xD

But who'd go through the trouble of finding the GUI then hex editing out each byte

Originally Posted by flameswor10

OFcourse, That is possible. But that'd mean hex editing out 3 byte arrays, because I use 3 set of bytes to make my menu GUI xD

But who'd go through the trouble of finding the GUI then hex editing out each byte

A leecher duhh.

Encrypting FTW?

Code Water Marking

Post a Reply

Tags for this Thread