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

Trojan detected in the latest release #6

Closed
akxer opened this issue Dec 28, 2022 · 2 comments
Closed

Trojan detected in the latest release #6

akxer opened this issue Dec 28, 2022 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@akxer
Copy link

akxer commented Dec 28, 2022

Detected: Trojanscript/Wacatac.H!ml
Status: Active
Active threats have not been remediated and are running on your device.
Date: 29-12-2022 01:09
Details: This program is dangerous and executes commands from an attacker.
Affected items:
file: C:\Users\testuser\Downloads\rule34.us.Downloader-win-x64\rule34.us
Downloader.exe

@IBangedMyToaster
Copy link
Owner

Hey akxer, thanks for letting me know.
Ill look into this and keep you updated

@IBangedMyToaster IBangedMyToaster self-assigned this Dec 29, 2022
@IBangedMyToaster IBangedMyToaster added the bug Something isn't working label Dec 29, 2022
@IBangedMyToaster
Copy link
Owner

IBangedMyToaster commented Dec 29, 2022

@akxer I have tweaked the Project and can’t seem to reproduce the error anymore. In case the error persists, I would advise you to manually allow the program to run in the security settings or deactivate the real-time protection while downloading the release.

It is interesting to know that this detection is a result of the defender’s machine learning regarding the real-time protection and is in fact a false positive.

Though this machine learning is really used throughout Defender's operation, it's most prevalent within certain specific detections which are designated by a suffix of "!ml" attached to the end of the detection name, which you should note is included in the one which detected your app.

Since these detections are related specifically to machine learning, they are inherently also found via real-time protection, so manual or automated scans will not find them.

Let me know if this workaround did the trick for you.

@IBangedMyToaster IBangedMyToaster closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants