Solved

Webroot flags ad.yieldmanager.com on yahoo sites

  • 26 December 2012
  • 5 replies
  • 1509 views

Hi, I'm running Webroot SecurityAnywhere v8.0.2.96 on a laptop PC running Windows XP.  I haven't done anything custom to it with respect to the configuration - just using the defaults to my knowledge.  My browser is Firefox.
'
Tonight when I go to finance.yahoo.com or flickr.com or search.images.yahoo.com, Webroot starts flagging ad.yieldmanager.com as suspicious site containing malicious code.  From everything I've been able to find online, it's just putting cookies on the browser.
 
Has this happened to anyone else?  Why is webroot generating these warning messages?  What should I do?
 
The strange thing is that my girlfriend's Windows7 laptop PC is also running the same version of Webroot and it doesn't flag the same sites when I go to them on that machine.
 
Thanks in advance!
 
Edit: Here is an image below of part of the screen showing the warning.
 

icon

Best answer by MikeR 6 January 2013, 19:59

View original

5 replies

Userlevel 7
Thank you for the detailed information, joross.
 
There may be an infection on your machine that is re-routing you to ad.yieldmanager.com even though you are entering other sites into your address bar in an attempt to capture log in details and personal information. Please Open a Support Ticket so that we can investigate further.
Thanks for the advice. Support Ticket submitted.
Userlevel 6
Badge +21
I encountered it yesterday also upon logging into Yahoo Mail.  So I just closed the browser and re-logged in with no issues.  Probably at that particular instance, the ad service yahoo is using was trying to push an ad that was flagged rather than the yahoo mail service itself.
Userlevel 7
Thank you for submitting the ticket. Better to be safe in situations like this.
 
The technician has requested logs through the support system and once you have replied it will be investigated further.
Userlevel 7
The site was being blocked and we have removed it from our servers. The block should not happen again and it can be set to Allow because it is not malicious.

Reply