Malware on ScubaBoard?

[SuPrBuGmAn]

Yeah, I got a warning again today too.

Atleast you guys have figured out there's a problem, only took three pages before the denial stopped. An improvement over the last site support thread I checked(which never was really resolved for me - the window hopping to the left thing).

 

[EastEndDiver]

I am getting a warning that says everytime I go to a thread or log on:

Web Attack: Malicous Javascript Website 2.

 

[deeper thoughts]

I am getting a warning that says everytime I go to a thread or log on:

Web Attack: Malicous Javascript Website 2.

I started getting this hit this morning. It went away and now its back

 

[CT Sean]

Getting the same thing this morning on Firefox

 

[gypsyjim]

I got the warning on both Firefox and IE this morning, and only for our SB site. I also noticed that, as NetDoc said, the site went into maintanence shutdown. Having that happen automatically in such an attack is probaly a good thing.

Good luck. HATE to see this site abused in such a way.

 

[fjpatrum]

I get the same warnings as GypsyJim. I can't even view anything of the site using Firefox 3.6.21. At least on IE I can view it but things are definitely hokey and I keep getting a "script running that is causing IE to respond slowly" every time I refresh a page or view a different page.

 

[ScubaSteve]

Same attack / warning here


I have cleared my cache and I'm still getting the warning and refusal to let me past.....using Chrome if that matters


Sent from my iPhone using Tapatalk

 

[gypsyjim]

I get the same warnings as GypsyJim. I can't even view anything of the site using Firefox 3.6.21. At least on IE I can view it but things are definitely hokey and I keep getting a "script running that is causing IE to respond slowly" every time I refresh a page or view a different page.

Exactly the same results.

Still cannnot access the site from Firefox, and only by putting the address into IE myself, rather than from a search engine.

 

[Mike]

Got this today

 

[redacted]

Something is back but probably not new. My alert told me that a problem was last detected on 15 Oct.