Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Randomness-based obfuscation]: false control flow, file size control, many to one file converter #35

Open
nacho00112 opened this issue Feb 14, 2024 · 7 comments

Comments

@nacho00112
Copy link

Due to indeterminated results, this may stop deobfuscators

@billythegoat356
Copy link
Owner

hey, what do you mean?

@nacho00112
Copy link
Author

Going into more detail, at this point you may want to use ast obfuscation instead of token obfuscation:

  1. Randomized false control flow

    You could generate false control flow and mix the real code logic with it, everything in a random and confusing way,
    A database (json?) May be handy here, like, with a list with variable names to use in the generation
    And other stuff you could need, this will probably require a more sophisticated analysis of
    The python code, to create false control flow that looks real and that provides great camouflage
    To the real code logic, that's why I mentioned ast

  2. File size control

    That is, that you can control how much false control flow you want in the code,
    The more, the bigger the file, that might increase obfuscation level, or you could determine this automatically based on real code's size

  3. Source code directories to one single file converter

    There are already libraries that do this, just imagine a large codebase of hundred of files
    Compressed in one simple python file, that would be a plus in the obfuscation,
    This may also need some randomization to avoid deobfuscators reversing this

@nacho00112 nacho00112 changed the title Randomness-based obfuscation [Randomness-based obfuscation]: false control flow, file size control, many to one file converter Feb 14, 2024
@billythegoat356
Copy link
Owner

I see what you mean
This is a nice idea, but sadly i made this obfuscator before learning about AST
It's not in my projects anymore, but it's definitely a smart way of stopping deobfuscators!

@nacho00112
Copy link
Author

Yeah, because once the obfuscation finish, the values of the random variables are lost,
So, you prefer considering this in a new project instead of adding to hyperion
Or you do no longer want to create obfuscators?

@billythegoat356
Copy link
Owner

I am no longer active on github and public projects like that. I am mostly doing personal projects
So this idea will most likely not happen :(

@nacho00112
Copy link
Author

That's sad, it was a quite famous project I liked it, if you ever have some code in your projects to publish you might want to obfuscate it, if that happens I hope you come back

@billythegoat356
Copy link
Owner

billythegoat356 commented Feb 15, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants