The original PowerShell script itself is clean and does not trigger any malware warnings when uploaded or scanned. The issue seems to arise only after converting it to an EXE.
Has anyone encountered similar false positives when using PowerShell Pro Tools for EXE conversion? Are there any recommendations or best practices we can follow to avoid this issue? We are looking for a way to deliver the EXE without it being flagged as malicious.
Any help or guidance would be greatly appreciated!
Tool: Visual Studio, Visual Studio Code, PSScriptPad, PowerShell Module
Version: