ensiform Posted February 29, 2016 Share Posted February 29, 2016 Never had this show up before, so not sure if its a false positive or not. Thought I should bring it to your attention in case there's an issue on the server. Link to comment Share on other sites More sharing options...
IATW Posted February 29, 2016 Share Posted February 29, 2016 I have this message too and it's a false positive, i have the confirmation from the eset team . You have to wait the update. Link to comment Share on other sites More sharing options...
Som Posted February 29, 2016 Share Posted February 29, 2016 I've gotten this message on three separate websites I normally visit this morning Link to comment Share on other sites More sharing options...
Steven P. Administrators Posted February 29, 2016 Administrators Share Posted February 29, 2016 I have reported it, I can only assume that it was flagged because it contains the website name and isn't hosted by us, but it is basically the global script for our inline ads served via GPT. Link to comment Share on other sites More sharing options...
Tomo Posted February 29, 2016 Share Posted February 29, 2016 (edited) It's a known issue with the latest Eset definition, Eset are currently working on it. https://forum.eset.com/topic/7567-jsscrinjectb-and-htmlrefreshbc-false-positive/ Link to comment Share on other sites More sharing options...
Torolol Posted February 29, 2016 Share Posted February 29, 2016 (edited) i'm still using Feb-27 virus database (13097 20160227 version) and the NOD32 aren't (false postively) flagging for me Link to comment Share on other sites More sharing options...
Tomo Posted February 29, 2016 Share Posted February 29, 2016 17 minutes ago, Torolol said: i'm still using Feb-27 virus database (13097 20160227 version) and the NOD32 aren't (false postively) flagging for me That's because it's an issue with 13102 Quote After the update 13102, we started receiving reports about "JS/ScrInject.B" and "HTML/Refresh.BC" detections on various websites. The update was stopped immediately to mitigate the impact on users. A new engine update 13103 is being prepared that will address the issue. In the mean time, as a hotfix you can switch to pre-release updates and then back. We apologize for the inconvenience. Link to comment Share on other sites More sharing options...
IATW Posted February 29, 2016 Share Posted February 29, 2016 It's ok for me now with the 13103 definition version Link to comment Share on other sites More sharing options...
Steven P. Administrators Posted February 29, 2016 Administrators Share Posted February 29, 2016 7 minutes ago, ffm76600 said: It's ok for me now with the 13103 definition version Thanks for the confirmation Link to comment Share on other sites More sharing options...
Recommended Posts