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
Add memory obfuscation? #661
Comments
This is something you will have to ask @Smug246 about, but from my recent knowledge, he dosen't work on Luna too often, so we'll have to wait and see. You can also just edit the |
this is a cool idea but as trickey said im very busy with school these days so something like this won't be added any time soon. your welcome to open a pr |
I'll do my best but I can't assure you that it'll work. I'll see what I can do. Would you think it should be fully compatible with any OS that runs the script or specific methods for specific OSes? Because if it's the latter an optional step in the readme for each OS would be much easier Also, would a system corrupter be a good idea? To prevent manual threat response for example resetting a password, etc? |
i think focusing on the windows os is fine i don't really support any others. system corrupter is a good idea but more for a rat. a grabber just wants the information. id rather it not break there pc. |
For Windows, there is an already-made app. I mentioned it in my original suggestion. As for the corrupter, maybe just having it or a rouge functionality as an option? |
On Wed, 13 Mar 2024 at 12:00, MasterCraft6969 ***@***.***> wrote:
this is a cool idea but as trickey said im very busy with school these
days so something like this won't be added any time soon. your welcome to
open a pr
I'll do my best but I can't assure you that it'll work. I'll see what I
can do. Would you think it should be fully compatible with any OS that runs
the script or specific methods for specific OSes? Because if it's the
latter an optional step in the readme for each OS would be much easier
Also, would a system corrupter be a good idea? To prevent manual threat
response for example resetting a password, etc?
i think focusing on the windows os is fine i don't really support any
others.
system corrupter is a good idea but more for a rat. a grabber just wants
the information. id rather it not break there pc.
For Windows, there is an already-made app. I mentioned it in my original
suggestion. As for the corrupter, maybe just having it or a rouge
functionality as an option?
yes potentially adding another tab on the UI named Rogue Options or
something would work nicely
… —
Reply to this email directly, view it on GitHub
<#661 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXU6Q7VGMF3SOAGXQI44WL3YYA5UBAVCNFSM6AAAAABD6BKTRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJUGIYTMMZXGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I'll look into it then, but it'll take some time if I decide to go for it, as I am also busy with school |
Something like shellcode fluctuation, and it stays silent until when the OS tries to shut down (with scheduling or systemd) then run so at best the AV will block it and the victim won't be alerted quite yet.
The text was updated successfully, but these errors were encountered: