Antivirus reporting PS Script as trojan

I temporarily disabled the AV & installed it. Thats the only way out for now I guess

Hi,

I assume this happened with the Devolutions Gateway installer? We install a copy of the DevolutionsGateway PowerShell module and call it during the installation to configure Devolutions Gateway. This is odd, it is code signed, and has never been flagged before by an AV. Can you try installing it separately and see if your AV flags it?

https://www.powershellgallery.com/packages/DevolutionsGateway

Best regards,

Hi,

I assume this happened with the Devolutions Gateway installer? We install a copy of the DevolutionsGateway PowerShell module and call it during the installation to configure Devolutions Gateway. This is odd, it is code signed, and has never been flagged before by an AV. Can you try installing it separately and see if your AV flags it?

https://www.powershellgallery.com/packages/DevolutionsGateway

Best regards,

Got this message, but when I selected Yes to All, it installed just fine.

Hi,

PSGallery is untrusted by default, so the prompt is expected. In your original error, the AV appears to have flagged the DevolutionsGateway module when it was initially imported, so can you try:

Import-Module DevolutionsGateway

And see if the AV kicks in as the module is loaded. If it works, then the AV is likely unhappy about the same PowerShell module being installed, loaded and called from inside an MSI installer.

Best regards,

Hi,

PSGallery is untrusted by default, so the prompt is expected. In your original error, the AV appears to have flagged the DevolutionsGateway module when it was initially imported, so can you try:

Import-Module DevolutionsGateway

And see if the AV kicks in as the module is loaded. If it works, then the AV is likely unhappy about the same PowerShell module being installed, loaded and call from inside an MSI installer.

Best regards,

Hi,

We have reported this false positive to Bitdefender, we don't know when they'll process it, but at least it is sent. In the meantime, I would recommend adding an exclusion rule.

Best regards,