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
Win-PS2EXE generating antivirus error #4
Comments
Hello Duxchux, it is the fate of programs generated with PS2EXE that they are sometimes identified as malware. Finally, compiled PowerShell scripts are executed, which is admittedly suspicious. The only hope is to report this to the producer of the antivirus software with the request for correction. I tested some compiled PowerShell scripts against VirusTotal and noticed, that Avast treats compiled scripts always as virus if they are generated with the switch "-NoConsole". I generated a sample and sent it to Avast with their false positive form. I hope they will correct this. Greetings Markus |
Thanks Markus for your quick response. Hopefully Avast can figure out how
to turn off the false positive for using such a (I thought) common switch
to prevent displaying the PowerShell console during script execution. I'm
very new to PowerShell, so I'm still learning.
As popular as PS2EXE and Avast are, I'm shocked that this issue hadn't been
uncovered in the past. Possibly something Avast changed? Anyway, if you
wouldn't mind letting me know when/if you receive positive feedback from
Avast that this has been resolved on their end, I would greatly appreciate
it.
Thanks again. Keep up the great work!!!!
Chuck
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
…On Fri, Sep 18, 2020 at 3:40 AM MScholtes ***@***.***> wrote:
Hello Duxchux,
it is the fate of programs generated with PS2EXE that they are sometimes
identified as malware. Finally, compiled PowerShell scripts are executed,
which is admittedly suspicious. The only hope is to report this to the
producer of the antivirus software with the request for correction.
I tested some compiled PowerShell scripts against VirusTotal and noticed,
that Avast treats compiled scripts always as virus if they are generated
with the switch "-NoConsole". I generated a sample and sent it to Avast
with their false positive form.
I hope they will correct this.
Greetings
Markus
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARAJMM5AEENZACQCXAIWRKDSGMFHHANCNFSM4RNOJELQ>
.
--
-- Chuck
___________________________________________
*DuxChux@gmail.com <DuxChux@gmail.com>*
*___________________________________________*
|
Closed since no response for over 2 weeks |
Attempting to run Win-PS2EXE.exe as Administrator, compiling a simple PowerShell script (Write-Host "This is a test") and Avast antivirus is marking the .EXE output file created as a virus (screenshots attached). No matter what PS script I attempt to compile, Avast doesn't like it. What am I doing wrong, or should I simply turn off Avast when compiling?
PC is Windows 10, latest .NET version, PowerShell 7 is installed, but this simple code doesn't use new PS7 features. I have run virus check on the entire PC not just select files and no virus was found.
Thank you in advance for your help.
-Chuck
The text was updated successfully, but these errors were encountered: