sensepolew.blogg.se - Pyinstaller windows

If just one or two are detecting a virus, you should be on the safe side.

I have uploaded the exe to to check it with many scanners.

Keep in mind that the exe files you generate yourself are unique (as a consequence, the Avast scanner usually returns a message "you have found a rare file, we are doing a quick test", and delays execution for 15 seconds to perform a more thorough test). Avira put that file into quarantine since it was considered potentially dangerous (due to heuristics, which means that some segments look typical for a virus, but no virus is actually found). I had a similar problem with a pyinstaller exe under Windows.

exe launcher that it created won't be considered a Trojan? Is there anything else I can do with PyInstaller to make it so that the. Hopefully they will back off on whatever it is that they thought they were trying to detect. exe file in question to AVG for their analysis. but still I'm concerned that it is not just AVG giving a false positive. Now I can't say that these other scanners are ones that I have heard of before. Rising Malware.Generic.5!tfe (thunder:5:ujHAaqkyw6C)ĬrowdStrike Falcon (ML) malicious_confidence_93% (D)Įndgame malicious (high confidence) 20170503 SentinelOne (Static ML) static engine - malicious Which shows that 11 out of 61 scanners detect a problem: TheHacker Trojan/Agent.am exe file to VirusTotal I get this analysis: At first I just thought it was a false positive in AVG, but submitting the. exe file used to start the program (in the folder created by PyInstaller that has all of the Python "guts"). My AVG Business Edition AntiVirus just started complaining with today's update that the program has an SCGeneric Trojan Horse in the main. About a month ago, I used PyInstaller and Inno Setup to produce an installer for my Python 3 script.