Jump to content

False Positive: MachineLearning/Anomalous.100% on VS 2017 vb.net debug


Recommended Posts

  • Staff


Thanks for reporting this to us. To clarify this some more, our machinelearning engine detects as "Anomalous", not really malware. So that means, it triggers on some anomaly design, unfinished builds, sections without content, etc etc...  This is detected correctly as anomalous.

This is what Malware does a lot as they change almost hourly, hence why this additional protection.

So if you are a developer, I suggest you exclude the working directory from detection. Once it's final and ready to be shared with others, in most cases it won't be detected anymore since it won't trigger the "anomaly" anymore either.

In case a "final project" is still detected, please let us know (include the sample), so we can add it to the learning as well to prevent this in the future.




Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.