A Lua sandbox implementation is a horrible idea, people will just crash your plugin, or worse escape the sandbox and run malicious code from your plugin.
I mentioned it as an alternative that you may come onto by yourself and then I posted a reason to refute the hypothetical idea you (in my train of thought) generated (Lua sandbox) (confusing sentence; what I’m saying here is I thought of what you could’ve thought of doing next and then a method on how to bypass what you thought of doing next)
I understand where you’re coming from when wanting to focus on basic back-doors however, when the basic back-doors are patched they are just going to simply fix the problem by using a more advanced method, and they will continue to do that. It will get to a point where your plugin is unable to contain the extreme amount of logic to intelligently analyze the malware. And if this is going to be for “basic” back-doors then why make it cost money. If the back-doors are so basic then tons of other programmers could probably reverse engineer the backdoor and easily create their own plugin to do exactly what yours does (for free!)
I agree with you, however I do want to get this better everyday by launching updates.
One Kronos’ feature is getting user installed plugins and scanning them for backdoors. This one can be easily made buut, it will also scan for the required ids.
If someone does stuff like
require(x) --// and x is a backdoor (required id will be scanned, inserted using GetObjects)
Kronos will move that script into quarantine for being a backdoor loader.
I do hope to see good feedback on the plugin, I’m positive about Kronos being 1st Plugin when it comes to malicious stuff detecting.
I do agree with this. Exploiters have gone through absurd amount of work and reverse engineering just to exploit my game. No one should ever under-estimate how much time they have on their hands :c
I’ve made a few backdoors in my time. Obviously not for actual malicious use, but for a learning experience - I wanted to see what I could do.
I can say that it is a fun experience. Just like you might be hooked or motivated to make your game, an exploiter is hooked and motivated to make an exploit for something (unless they’re the average script kiddie- but they don’ tend tot make backdoors). Just like that feeling you get when you’ve spent hours fixing a bug and it finally works - an exploiter feels rewarded when they finally get their exploit done.
Never say that “Literally no one would bother to do stuff like that” - they will. It’s just another challenge for them to have a crack at (or potential business opportunity, exploits have made some serious money).
TD;LR: Always develop knowing that someone, anyone, will take a serious shot at cracking it - someone eventually will.
Each time I use Kronos, this prints out in the output:
If I click on the warning, nothing happens. This is confusing, since I don’t know what’s loading this.
When looking at the source, I seem to understand that Kronos is somehow detecting that nil contains a backdoor???
Also, I think the plugin could be 100x better if there was a UI, since it would be more intuitive to the average user.
I tested this plugin on all the top free models **created by Roblox**, and it managed to detect one of the scripts to be a Fire/Instance virus:
You might want to mention that they sometimes might happen, to not spread misinformation.
It brings up this warning for the original model by Kohltastrophe, I believe what the scanner’s picking up is what the script uses to automatically update itself to the latest. It uses the old LoadAsset method to get the latest version.
i was not finding them in the game by myself. I figured out that the script was inside a model in my account’s inventory, I removed from my inv. Damn hacks.
