SailNet-Hosted Attack/Badware Pages?!?!

[RhythmDoctor]

This morning Firefox started blocking my access to this site. Apparently Google's "safebrowsing" feature has logged 8 exploits on this site. My guess is that either the site has been hacked by a third party, or some of the ads that are posted on the site are themselves exploits.

I'd appreciate it if the moderators could check this out. All the documentation on this safebrowsing feature says that legitimate sites are hacked all the time, so a site that has been "safe" in the past is not necessarily safe currently.

For more information on what exploits Google has found on this site, the below link will run the forum though Google's filter and report what they found:

http://www.google.com/safebrowsing/d...iling-related/

[SEMIJim]

Wonderful:



Clicking on "Why was this page blocked?" yields:



Even if I wanted to disregard the problem: I can't browse SailNet, now, without those two popping-up on every page load. (The warning page's "ignore this warning" selection, and the resulting requester, apparently are disregarded by the "badware" detector.) So SailNet is unusable unless I want to disable the "badware" detector entirely. Which I've done for the purposes of posting this. I'm not inclined to leave that disabled.

Jim

[administrator]

definately not hacked. we have subscribed to google list of trusted sites and yesterday they discovered some wield code in one of the ads our ad broker is serving up. we received notification from google and we are removing the code that serves up that particular ad. definintely not hacked.

[lydanynom]

On the bright side, the site loads great without /sailnet/box_.php. At least we know what to block at our proxies now. ;-)

[administrator]

we're fixing the box_.php error this morning also.

thanks!

[lydanynom]

Originally Posted by administrator

we're fixing the box_.php error this morning also.

thanks!

No, my point was that it is much better like this, and an easy way to keep it so ought to be to tell our adblockers and filtering proxies to continue preventing that code from loading.

[kaneb]

We are fully aware of the isssue and are in communication with Google who has sounded the alert. While IE continues to work, this issue has effected browsing sailnet.com in firefox.

Thank you for your patience

[administrator]

Originally Posted by lydanynom

No, my point was that it is much better like this, and an easy way to keep it so ought to be to tell our adblockers and filtering proxies to continue preventing that code from loading.

the box code is our own code that retreieves information from the shop.sailnet.com store and diplays relevent items in the left column.



Jeff J

[remetau]

I'm still using Firefox, but I had to turn off the "Block reported sites" option.

[lydanynom]

Originally Posted by administrator

the box code is our own code that retreieves information from the shop.sailnet.com store and diplays relevent items in the left column.



Jeff J

Right. My point is that the pages load much more quickly for me without that stuff there. I would never have thought to block it explicitly otherwise, so it is a happy coincidence that it was broken for a while so we could see what a bottleneck it was.