Wonderful Javascript #
Posted Thursday 14th May 2009 22:26 GMT
Ready to admit that javascript is a mistake for web browsers?
This post has been deleted by a moderator
Posted Thursday 14th May 2009 22:26 GMT
Ready to admit that javascript is a mistake for web browsers?
Posted Thursday 14th May 2009 22:26 GMT
The obfuscated JavaScript on compromised sites (which Sophos intercepts as Troj/JSRedir-R) accounts for about 42% of all of the infected webpages we've seen in the last week.
That's a mightily impressive six times more infections than the tried and trusted malicious Iframe attack of Mal/Iframe-F.
We've published some further information and stats on our site at http://www.sophos.com/blogs/gc/g/2009/05/14/malicious-jsredir-javascript
I'd recommend that surfers check their protection is up-to-date and fighting this one.
Posted Thursday 14th May 2009 22:49 GMT
I don't allow JavaScript to run on website, use any Adobe products and only update my site (that doesn't allow JavaScript) by dumping the files into its file share. Nor do I click on any Google advertisements....
Besides, Flaws in Adobe software is old news
Posted Friday 15th May 2009 09:36 GMT
..Kvnt Eurtgruel in this?
Posted Friday 15th May 2009 09:36 GMT
Good thing that we both wasted time posting pointless stuff!
Posted Friday 15th May 2009 09:36 GMT
Is anyone still using Adboe Reader??? I thought all the smart people had moved over to Foxit.
Posted Friday 15th May 2009 14:11 GMT
Not just Foxit, there are a host of alternatives, for Windows and non-Windows alike. KPDF is what comes preinstalled on my OS/distro of choice.
Posted Friday 15th May 2009 14:34 GMT
I work for a fairly large hosting provider and we're seeing it here too.
Interestingly, we're also seeing a .htaccess being dropped into the root ftp folder which attempts to perform various redirects, set (compromised) custom error docs and calls some perl scripts.
Ammusingly they don't upload the error docs, scripts and their .htaccess is malformed, which simply took the sites offline instead. If the error docs had been correctly uploaded then they'd have spread via the 500 internal server errordoc though.
The reason I mention it is because it's from the same 'straight-in' access from compromised FTP accounts. I cleared out about 15 infections yesterday - of which all logged in first time with the right details.
Sign up, sign up for The Register's weekly IT security newsletter - click here