Referring to the first two postings in this thread, browser ad and JavaScript blocking extensions and the like would not have prevented this activity.
It appears something was installed manually. It could have be standalone software. If it was then the following were applicable:
1. The software was installed prior to Eset being installed.
2. Eset's PUA protection was/is not enabled.
3. Eset's PUA detection was ignored and the poster allowed the software installation.
Another possibility is the poster either explicitly or inadvertently installed a browser extension that contains the javacript code being detected.
PERRYGOGAS gave kudos to itman in Removal of JS/ScrInject.b ???
