Oct 5, 2017 04:45 AM
(This post was last modified: Oct 6, 2017 05:49 PM by Velo.)
So, I have a program that compiles source code from my text file into an executable.
I need EACH Compilation to be 100% unique/different
Currently I have random junk code, random variables/method names and SOME function randomization, etc; 50/50 chance of it using Thread.Sleep and Task.Delay, Application.Exit/Environment.Exit
What are some other good ways to enhance my signature uniqueness?
So far with sigbench im getting about 86% difference
Need this higher.
Thanks.
Group each method code into multiple 'blocks', for each block it should be safe to change the order of the lines in it.
Also, substitute the method call with the actual method implementation (this depends on the structure of the method).
I'm not really sure variables names would make difference, don't they compile to memory addresses after all? make sure you're building for 'Release' not 'Debug', 'Debug' contains much more info which could give false increase in the difference rate.
Finally, you can mess up with the result code and add some NOPs around.
Have a cool signature? hit me up and I might use it.
DO NOT DEAL WITH THIS MEMBER
(Oct 5, 2017 04:45 AM)Velo Wrote: 50/50 chance of it using Thread.Sleep and Task.Delay
I'm so fucking triggered.
DO NOT DEAL WITH THIS MEMBER
(Oct 5, 2017 04:45 AM)Velo Wrote: 50/50 chance of it using Thread.Sleep and Task.Delay
What about a 50/50 chance of it using Environment.Exit and Application.Exit?
or a 50/50 chance of memory leaks and copy pasta dripping out of the cd tray
(Oct 5, 2017 04:45 AM)Velo Wrote: So, I have a program that compiles source code from my text file into an executable.
I need EACH Compilation to be 100% unique/different
Currently I have random junk code, random variables/method names and SOME function randomization, etc; 50/50 chance of it using Thread.Sleep and Task.Delay
What are some other good ways to enhance my signature uniqueness?
So far with sigbench im getting about 86% difference
Need this higher.
Thanks.
thread.sleep and task.delay are two completely different things.
considering you're replacing things with things you've googled as alternatives i feel like this project isnt for you.
(Oct 6, 2017 07:33 AM)Ranger. Wrote: What about a 50/50 chance of it using Environment.Exit and Application.Exit?
again, two completely different things.
DO NOT DEAL WITH THIS MEMBER
Oct 6, 2017 11:18 AM
(This post was last modified: Oct 6, 2017 11:20 AM by Ranger..)
(Oct 6, 2017 10:43 AM)GrandOlFlag Wrote: thread.sleep and task.delay are two completely different things.
considering you're replacing things with things you've googled as alternatives i feel like this project isnt for you.
again, two completely different things.
They're not completely different things, dumb-ass. They serve almost the same purpose (in each of the examples), which means that they're easily going to detected by any competent anti-virus. An anti-virus does not solely base a detection on a file-hash.
Stop trying so hard lmao.
(Oct 6, 2017 11:18 AM)Ranger. Wrote: They're not completely different things, dumb-ass. They serve almost the same purpose (both of the examples), which means that they're easily going to detected by any competent anti-virus. An anti-virus does not solely base a detection on a file-hash.
Stop trying so hard lmao.
no they don't.
they achieve the same goal but differently.
Enviroment.Exit will kill the process disallowing you the opportunity to close and flush resources should only be used usually as last resort.
Application.Exit raises the OnClose event allowing you to dispose and take care of resources.
DO NOT DEAL WITH THIS MEMBER
(Oct 6, 2017 11:22 AM)GrandOlFlag Wrote: they achieve the same goal
Exactly what I said. Stop trying to out-think this shit when you clearly know that I mean that they both END the process (Application.Exit might not end the process if there's a form preventing it from doing so though.)
(Oct 6, 2017 11:24 AM)Ranger. Wrote: Exactly what I said. Stop trying to out-think this shit when you clearly know that I mean that they both END the process (Application.Exit might not end the process if there's a form preventing it from doing so though.)
that isn't the point here
task.delay and thread.sleep both cause a delay whether its async or sync but to say they're interchangeable is just ignorant.
THEY BOTH CAUSE A DELAY SO WE CAN 50/50 CHANCE IT SCREW THE REAL PURPOSE
(Oct 6, 2017 07:29 AM)Ninja Wrote: I'm so fucking triggered.
LOL'd for like 5 minutes after reading this.
This is NOT for altering virus detection ratios.
DO NOT DEAL WITH THIS MEMBER
I think you're in way over your head if you actually have to ask this.. How about you develop your terrible p2c using your own research?
DO NOT DEAL WITH THIS MEMBER
For each generated code to be 100% unique you need a metamorphic engine- see my tutorials series I've posted.
From the context I suggest you keep working out the infinite numbers of PI until you reach a number so long that it fills up the RAM and gives you a nice and sexy BSOD!
It will take dedication, but with the power of hope, anything is possible.
|