[GH-ISSUE #156] Maleware detected on output executable file #147

Closed
opened 2026-02-26 12:20:37 +03:00 by kerem · 2 comments
Owner

Originally created by @ghost on GitHub (Feb 6, 2021).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/156

Is that true that you did that to us? 🤔
236

Originally created by @ghost on GitHub (Feb 6, 2021). Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/156 Is that true that you did that to us? 🤔 ![236](https://user-images.githubusercontent.com/59511669/107130258-6ef1c700-68aa-11eb-8e0b-d3be7afb9e6a.PNG)
kerem 2026-02-26 12:20:37 +03:00
  • closed this issue
  • added the
    duplicate
    label
Author
Owner

@brentvollebregt commented on GitHub (Feb 6, 2021):

Did you look at previous issues that talk about this? #122 and #125 are very similar.

Has been raised in the PyInstaller repo at pyinstaller/pyinstaller#4633 and the same message is given:

Please contact you anti-virus vendor. There is nothing we can do about this false positive.

If your anti-virus vendor considers one of the files included in the PyInstaller distribution or a file generated by PyInstaller to be malicious, there is nothing we can do about this. Even if we'd change our code, they'd change their pattern and the race starts again.

See this mailing-list thread and other tickets for his topic.

You literally have access to the source code of auto-py-to-exe and can even look at the source of it on your own machine after getting it from PyPI. Did you look at that before raising this? Where is your evidence aside from a false positive?

To be honest, that title is quite rule in my opinion.

<!-- gh-comment-id:774551593 --> @brentvollebregt commented on GitHub (Feb 6, 2021): Did you look at previous issues that talk about this? #122 and #125 are very similar. Has been raised in the PyInstaller repo at pyinstaller/pyinstaller#4633 and the [same message is given](https://github.com/pyinstaller/pyinstaller/issues/4633#issuecomment-575537881): > Please contact you anti-virus vendor. There is nothing we can do about this false positive. > > If your anti-virus vendor considers one of the files included in the PyInstaller distribution or a file generated by PyInstaller to be malicious, there is nothing we can do about this. Even if we'd change our code, they'd change their pattern and the race starts again. > > See this [mailing-list thread](http://www.mail-archive.com/pyinstaller@googlegroups.com/msg05002.html) and [other tickets for his topic](https://github.com/pyinstaller/pyinstaller/issues?q=is%3Aissue+virus+is%3Aclosed). You literally have access to the source code of auto-py-to-exe and can even look at the source of it on your own machine after getting it from PyPI. Did you look at that before raising this? Where is your evidence aside from a false positive? To be honest, that title is quite rule in my opinion.
Author
Owner

@brentvollebregt commented on GitHub (Feb 6, 2021):

Closing as this is a duplicate of #122.

If you do find some supporting evidence that I have done something malicious in this project - feel free to comment here as I would love to hear it.

<!-- gh-comment-id:774551816 --> @brentvollebregt commented on GitHub (Feb 6, 2021): Closing as this is a duplicate of #122. If you do find some supporting evidence that I have done something malicious in this project - feel free to comment here as I would love to hear it.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/auto-py-to-exe#147
No description provided.