Javinizer icon indicating copy to clipboard operation
Javinizer copied to clipboard

Bitdefender blocking javinizer from loading FYI

Open Freakboo opened this issue 2 years ago • 4 comments

Expected Behavior

Runs normally

Current Behavior

Powershell: javinizer: The 'javinizer' command was found in the module 'Javinizer', but the module could not be loaded. For more information, run 'Import-Module Javinizer'.

Bitdefender antivirus: PowerShell tried to load a malicious resource detected as Heur.BZC.ZFV.Boxter.341.17AF9D58 and was blocked. Your device is safe.

I dissabled it when using javinizer and re enable later, Im not sure how to add this type of exclusion.

Steps to Reproduce (for bugs)

Have both installed

  • Module version used: 2.3.3 & below works 2.4.0 & newer trips stupid bitdefender

  • Operating System and PowerShell version: win11 powershell 7?

Freakboo avatar Jun 17 '22 00:06 Freakboo

I have this same issue, and even adding scripts to exceptions does not seem to work.. I'm guessing BitDefender is looking at what the running script is going to do rather than letting people ignore the scanning of script.. For now the only solution seems to be just disabling the antivirus everytime you need to Javinizer.. Atleast until there is either update to the script itself, or until Bitdefender bothers removing the false negative

ghost avatar Sep 09 '22 15:09 ghost

I got it to work a while ago by adding powershell 7 to the exception with the extended scripts? Not sure if that's what you meant or you actually added the .ps1. GL Untitled

Freakboo avatar Sep 12 '22 01:09 Freakboo

I got it to work a while ago by adding powershell 7 to the exception with the extended scripts? Not sure if that's what you meant or you actually added the .ps1. GL Untitled

Doing it this way will leave you actually open for other vulnerabilities because now its not checking Powershell 7 at all

ghost avatar Sep 13 '22 14:09 ghost

Doing it this way will leave you actually open for other vulnerabilities because now its not checking Powershell 7 at all

... good point, I didnt think of that. ahhhh. Ill just have to go back to disabling it for for the duration of my use and enable it again.

Freakboo avatar Sep 23 '22 00:09 Freakboo