jQuery.com Compromised To Serve Malware
An anonymous reader writes jQuery.com, the official website of the popular cross-platform JavaScript library of the same name, had been compromised and had been redirecting visitors to a website hosting the RIG exploit kit and, ultimately, delivering information-stealing malware. While any website compromise is dangerous for users, this one is particularly disconcerting because of the demographic of its users, says James Pleger, Director of Research at RiskIQ.
People get upset when you call them incompetent for sourcing stuff out to foreign CDNs, but stuff like this happens all the time. It's not safe to pull stuff in from other sites for reasons which are obvious to anyone competent.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Or perhaps lets start hosting our own content again so when one of the big guys gets ass raped, only the big guys get ass raped.
did I just hear some relevent news on slashdot before i saw it on twitter?
today is a bright, shiney day!
THL phish sticks
The only good news in all of this is that there is no indication that the jQuery library was affected.
'The tyrant will always find pretext for his tyranny.' - Aesop's Fables
This is going to be a large one. Many small to medium websites use their cdn for hosting JQuery rather than pulling it down and hosting it themselves. Kinda feel a little better about hosting it myself now.
This is exactly the sort of reason I run requestpolicy, and jquery is always one of the ones I hate seeing because I know what it means to allow so many sites to talk to load code the same one, so it only ever gets a temporary exception, same for googleapis.
"I opened my eyes, and everything went dark again"
That's one of the main reasons I prefer hosting all the files myself. At least you don't compromise your IT-security or brandname if such a breach happend. The attackers clearly didn't know what damage they could have done if they used this breach correctly.
1. Change the CSS & Jquery javascripts that are used by millions of domains and websites.
2. Serve malware.
3. Profit.
I have always treated it like it's an external 3rd party, not the web site I'm visiting, and therefore not an entity I trust.
I've always viewed jquery as about as trusted as doubleclick or scorecardresearch. I don't know or care what you do, I didn't visit your site.
But then, I've learned not to trust the web in general.
With so many sites using this, dumping malware into it means you can get a whole lot of sites easily ... making this a fairly obvious target.
Lost at C:>. Found at C.
I wonder what their side of the compromise was. What could they want that a Malware company could provide?
This shows how dumb the hacker is. If you managed to hack jquery.com, it seems like the first thing to go after is the jquery library that's hosted there.
You mean... jQuery?
(for the record I use it where appropriate, but it's also way over/misused)
Probably not that dumb. If it's a watering-hole attack to go after developers rather than end-users to steal IP or go after high-volume websites in a less-indiscriminate way, then that would make sense.
it is illogical to lie and claim that it was compromised to serve malware. It was compromised to serve an additional malware. That is what happened. The headline uses Republican style logic. The only thing it didn't do was talk about how much the jQuery creators hate their users by spewing out such garbage that they shove down the throats of users. They are horrible people.
Did a little research on the Rig exploit, and I've come away a bit confused: if I hit the exploited site while using a Mac, could the Mac be infected, and if so how could I tell - and how could I remove it if so? Thanks in advance.
Yeah, I just turn your hosts file into my local DNS server and point everything at that. No point in copying host files around to every blessed machine.
Browser sniffer par excellence.
Or they wanted to see how quickly a penetration would be noticed, if at all, so that they could build a bigger exploit.
Do not look into laser with remaining eye.
Too bad the article it linked to used that almost unreadable light grey colour on the font. I took one look and decided not to bother. When I have to squint and struggle to see it, forget it. Who was the numbskull who came up with the idea that light grey on white is a good scheme for presenting type? Or was this a case of younger designers not giving a rat's ass about older readers? Fuck.
How dare you dismiss an entire organization as incompetent based on the selection of a popular and mature CMS platform?
It's the *3rd party* code that introduces the majority of exploits to the platform. The quality of code in the plugin/theme community is largely *crap* and deserves your misplaced ire.
Further, jQuery's use of WordPress is anything but standard: http://gnarf.net/jquery-and-wordpress/#slide1
And finally, I'm not really sure if the OP is accurate at all. The only affected domain seems to be jquery-cdn.com which doesn't appear to be an official domain in the first place. In the first link in the OP has a statement from the jQuery Foundation stating that they can't confirm ever being infected.
~jbr
The attack should be a concern because jquery.com visitors are devs and sysadmins. But I understand RIG is a Windows malware. Who trust Windows enough to use the same machine surf the web and to store precious keys?
Higher electrical bills, cpu, RAM & other forms of I/O too in running a local DNS machine (especially if/when it's a separate machine), as well as more room for error due to complexity/breakdown OR exploit (Kaminsky flaw etc. - patch yourself against it OR opt for TCP usage vs. UDP (which the latter LITERALLY DOUBLES dns overheads)).
* It's not a hassle to batchfile or cmdfile copy hosts around a network & they're less complex by far as well as less prone to error or exploitation as well (this can be setup to be automated IF you wish even from a central server in scheduled tasks (Windows) OR chronjobs (*NIX)).
APK
P.S.=> However, *IF* you don't mind those items noted above? Whatever works for you... apk
https://twitter.com/jquery/sta...
---------
There is no try at jedinite.com
I only posted twice in this article's response threads here http://developers.slashdot.org... and here (in reply to someone) http://developers.slashdot.org...
* You have issues, Mr. Impersonator - get over them!
APK
P.S.=> Bad impersonation too - you forgot my 'p.s.' I do @ the termination of my posts as well... apk
0.0.0.0 woitp.bestburaco.com
0.0.0.0 bestburaco.com
* Add those 2 lines to your hosts file & voila: You're "bulletproof" vs. this threat...
( Source for said protective data was digging into the source article here & it's actual TECHNICAL resource source RiskIQ -> http://www.riskiq.com/resource... )
APK
P.S.=> For added protection vs. such threats that utilize host-domain names (the vast majority), as well as for gaining added speed, reliability, & more (than better security too)? Well, you know:
APK Hosts File Engine 9.0++ 32/64-bit:
http://start64.com/index.php?o...
(Hey - it's "ME", & when hosts apply to solve a security issue or other problem? I post, since after all - it works!) ... apk