Closed joaocarrato closed 2 months ago
To prevent cracking, I've added a simple packer (in a way, this also reduces false positives). The injection method and the source code itself will inevitably trigger antivirus warnings in strict mode. If you don't believe me, you can try compiling it yourself and then check for any virus alerts.
Determining whether something is a virus isn't just about the number of virus alerts, but about checking whether it performs suspicious or dangerous actions on your system. (Basically, it's up to you to judge for yourself.)
To prevent cracking, I've added a simple packer (in a way, this also reduces false positives). The injection method and the source code itself will inevitably trigger antivirus warnings in strict mode. If you don't believe me, you can try compiling it yourself and then check for any virus alerts.
No problem mate, I really made a point of not doubting your project, I've been using it since the original which also gave virus alerts until you started updating it. I just wanted to better understand what was going on “behind the scenes”. I'll keep using it and try to tinker with it for study purposes! Thanks for your reply and thanks again for continuing the project.
Hello my dear, first of all I would like to thank you for providing the service of updating the project so that we can continue using it. However, I have always been curious about the detection of malware in the exe file. I'm studying reverse engineering and also malware analysis and even knowing that you leave the source code public, I couldn't help but notice the calls we have and also the SafeEngine Shielden protection. Some DeleteFile calls, CreateMutex and so on. Could you please explain these calls? I'm even asking to increase my knowledge of the subject. Thank you very much
PS: I'm not judging you.