-
-
Notifications
You must be signed in to change notification settings - Fork 705
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
Windows V62.3 triggers virus alert in Kapersky again (FYI) #2226
Comments
Hi!
Thanks for the report. It’s already been reported earlier in #2092.
Unfortunately, we’re not responsible for Kaspersky’s trojan list. It’s already been reported, but they don’t care. It’s definitely a problem in their virus detection heuristic (the executable contains Python code, and that’s seen as a threat), and we’re not powerful enough to fix a $700M-revenue company piece of software 😄. If you find a solution, don’t hesitate to add a comment here! |
Got a fast reply from Kapersky " Sorry, it was a false detection. It will be fixed. Best regards, Danila, Malware Analyst |
Yes, they remove the specific reported version quickly, but unfortunately don’t fix the heuristic that will detect future versions as virus. |
This is just for your information ...
the exe file triggered as of today 13-Aug-2024 with the current virus database in Kapersky.
Have sent it to Kapersky for reconsideration but it may cause others (Defender etc.) to trigger as well.
Is there anything to avoid this issue popping up with further releases?
I think it is not appropriate to ask anybody to switch their virus checker off in order to install it and then mark it as exception.
The text was updated successfully, but these errors were encountered: