Python Forum
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
pyinstaller false positives
#1
An executable produced by pyinstaller is automatically removed by my Norton antivirus.
I know this has been adressed by Buran (some time ago) and multiple sites offer the same
suggestion i.e. "compile a pyinstaller bootloader"... ? to counter false positives.
2 questions:
1) This happened overnight, 2 days ago I was happily using pyinstaller with no warnings.
Is it known what triggers this behaviour ?
2) The name of the "detected" "virus" is "Heur.AdvML.B" .
Why shouldn't I feed that to the exclusion list of Norton, looks kiss to me.
Or... some people suggest to pip install an older version of pyinstaller ?
thx,
Paul
It is more important to do the right thing, than to do the thing right.(P.Drucker)
Better is the enemy of good. (Montesquieu) = French version for 'kiss'.
Reply
#2
I found that I can restore the executable from Norton quarantine.
Scan it again with Norton, finding nothing this time.
Feed it to virusTotal, where 2 of the 50 detect a Trojan.
Each one a different Trojan.(?)
Much ado about nothing ?
Paul
It is more important to do the right thing, than to do the thing right.(P.Drucker)
Better is the enemy of good. (Montesquieu) = French version for 'kiss'.
Reply
#3
It is a known issue. As you could see, there are numerous different approaches to "solve" it. But ultimately it relies on the anti virus companies to "green flag" these executables so they don't get quarantined. To my knowledge, the best we can do is to report these events as false positives and hope for a fix in the future.
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  difference between «1 in [2] == False» and «(1 in [2]) == False» fbaldit 2 2,244 Apr-20-2020, 05:39 PM
Last Post: fbaldit

Forum Jump:

User Panel Messages

Announcements
Announcement #1 8/1/2020
Announcement #2 8/2/2020
Announcement #3 8/6/2020