You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using Ironman PowerShell Pro Tools to convert a PowerShell script (which includes a GUI interface via Windows.Forms assembly) into an executable (EXE). However, after conversion, the EXE is being flagged as trojan.marsilla by VirusTotal and other antivirus software.
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!
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Hello everyone,
We are using Ironman PowerShell Pro Tools to convert a PowerShell script (which includes a GUI interface via Windows.Forms assembly) into an executable (EXE). However, after conversion, the EXE is being flagged as trojan.marsilla by VirusTotal and other antivirus software.
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!
Thanks in advance!
The text was updated successfully, but these errors were encountered: