Replies: 1 comment
|
It's still flagged by MaxSecure. The main change is that I embedded the web panel assets (lots of JavaScript) into the executable; I suspect this extra content altered the binary enough to reduce signature-based detections on other engines, while MaxSecure still triggers (idk why). If you'd like to verify, you can open both executables (new and old one) in dotPeek and compare them to the code in the repository commits - there's no obfuscation, so the logic should match. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Looks like it's not detected as malware anymore? although, answers would be nice.
All reactions