Same here. One of my client sites reported this, and I’m able to duplicate the issue on my own computer.
To get around it, as the issue seems to be an infected VBScript or bad detection of a good VBScript, simply use some other browser besides Internet Explorer.
Chrome, Firefox, etc. will work fine, as those browsers don’t use VBScript.