30K WordPress Blogs Infected With the Latest Malware Scam
alphadogg writes with an excerpt from an article over at Network World: "Almost 30,000 WordPress blogs have been infected in a new wave of attacks orchestrated by a cybercriminal gang whose primary goal is to distribute rogue antivirus software, researchers from security firm Websense say. The attacks have resulted in over 200,000 infected pages that redirect users to websites displaying fake antivirus scans. The latest compromises are part of a rogue antivirus distribution campaign that has been going on for months, the Websense researchers said."
websites displaying fake antivirus scans
I didn't know McAfee had started targeting Web blogs now.
"That's the way to do it" - Punch
Why do they always focus on the crap that's left behind when they analyses these things? I want to know how they managed to get that stuff on those servers so I can check my own. Was is an old and vulnerable WordPress or was it some 0-day they used? For some reason they always focus on the effects and not on the causes.
At a guess, the ratio of Installs to Unpatched/Insecure Installs, both of the core WP software and its many, many 3rd party plugins and themes.
A *lot* of sites are either running old versions of software or have plugins/themes with gaping vulnerabilities that are no longer under active development.
"The Websense ThreatSeeker Network has detected a new wave of mass-injections of a well-known rogue antivirus campaign"
... moving on ...
How exactly are these sites infected in the first place?
"The page looks like a Windows Explorer window with a "Windows Security Alert" dialogue box in it"
Ahh so - nothing to read here
AccountKiller
The block 194.28.112.0/22 is simply all evil (I've documented it here in the past), there's no reason to send traffic to it at all, blocking it is a good option.
Never email donotemail@WeAreSpammers.com
Why bother using 0day exploits and payload droppers when the best infector is sitting right in front of the PC?
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Some of that is Wordpress' fault for not having an easy way to run mass upgrades. My employer has 15 different sites running on Wordpress and the fact that I have to log in to each one manually after upgrading the files and click a link to handle the database update is annoying.
Some of that is Wordpress' fault for not having an easy way to run mass upgrades. My employer has 15 different sites running on Wordpress and the fact that I have to log in to each one manually after upgrading the files and click a link to handle the database update is annoying.
This drove me nuts at my current job for about 2 months - you need Wordpress Network.
There's the easy way and the hard(er) way to do this:
This is the official easy way, but it's never worked for me (last tried in Spring of 2011). The nice thing is that it's all stuff built into WordPress, so you should be able to do it without any problems. I'd say it's probably worth giving this a try with one site, and if it works, run with it.
This is more down and dirty way that will definitely work, and is more or less how I did it. A little SQL editing never hurt anyone.
Also, this is a great companion to the bavatuesdays link. He goes on about his DNS in the first few paragraphs, but the second half of that post has some good details about where files need to be, and how links and such need to be updated.
Once you have a network, you a fantastic "Update Network" button. Boom. Take the rest of the day off.
Are you an idiot? The article is talking about WORDPRESS - a web application! Windows isn't involved!
For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
Most of my WP installs were infected because I am a slack ass. Here are the high level steps I took to solve the problem:
I may be missing something - again, I'm a slackass. Anyone else have other advice for our admin-challenged friends besides "get a real software package"?
By the way, I was trying to lock down one of my WP installs to only allow authed users access to posts. However, WP does not put the assets for post - usually in wp-content/uploads - behind the auth wall. It's just out there for the whole world to see. It was a simple fix to rewrite the .htaccess config for this directory to redirect to an auth script, but still it still shocks me how insecure this app is.
BTW: why is Adobe allowed to - by default - check the box on their flash updates to also install Norton on the victims computer? How many trusting civilians (think: grandmothers) end up with borked computers with conflicting AV programs solely due to corporate greed? I'm willing to bet this check box (if it even appears) is NOT checked by default in the EU market. Man, I miss government FOR the people...