-
|
my avast detected that has win32:malware-gen someone help me pls |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
|
oh god that was close |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, it's nothing úvù Reporting it as a false positive is probably the only way to make it get flagged less frequently for other users in the future. All ""win32:malware-gen"" means is that the files seems suspicious, but if that makes you uncomfortable you could always just install python, clone the repository, and run pesterchum.py directly. Python code doesn't need to be compiled so it's functionally the same in the end. |
Beta Was this translation helpful? Give feedback.
-
|
oh thx |
Beta Was this translation helpful? Give feedback.
-
|
ehm mmm |
Beta Was this translation helpful? Give feedback.
-
|
Hm? |
Beta Was this translation helpful? Give feedback.
-
|
welp |
Beta Was this translation helpful? Give feedback.
-
|
oh thx so much |
Beta Was this translation helpful? Give feedback.
-
|
now how i use it |
Beta Was this translation helpful? Give feedback.
Yeah, it's nothing úvù
Builds like this sometimes get flagged because they're unsigned and the exe is just not known to the antivirus. This can happen with both pyinstaller and cx_freeze. Builds packed with UPX may run into this issue more frequently as well.
Reporting it as a false positive is probably the only way to make it get flagged less frequently for other users in the future.
All ""win32:malware-gen"" means is that the files seems suspicious, but if that makes you uncomfortable you could always just install python, clone the repository, and run pesterchum.py directly. Python code doesn't need to be compiled so it's functionally the same in the end.