Live data from Hacker News

Huge attack on WordPress sites could spawn never-before-seen super botnet

arstechnica.com

31–40 of 86 posts

Re: Huge attack on WordPress sites could spawn never-before-seen super botnet

#31

Don't know if this is a dumb question: but would it be possible for a good party to use the same method to get admin access and install rate-limiting login plugins on all of these insecure WordPress blogs? Seems like that would be badass.

See this post for an explanation why it isn't a good idea: http://www.schneier.com/blog/archives/2008/02/benevolent_wor...

Re: Huge attack on WordPress sites could spawn never-before-seen super botnet

#32
Use a two-factor auth plugin like https://wordpress.org/extend/plugins/google-authenticator/ It works with the Google Authenticator app.

Duo Security is also good: http://wordpress.org/extend/plugins/duo-wordpress/

The WordPress.com team have already announced two-factor auth support for wp.com blogs, and are working on an official solution for wp.org sites: http://macmanx.com/2013/04/12/two-step-authentication-on-wor...

Re: Huge attack on WordPress sites could spawn never-before-seen super botnet

#33
post #6

Earlier quoted context omitted.

That's usually the first mod done for clients who insist on using WP. For a few clients specifically, we don't let any users set their passwords at all; they get a randomly generated password upon registering or reset; WP is a good platform that does a lot out of the box (performance could use some work too though), so I don't think we should throw the baby out with the bathwater. There's just some housekeeping that…

Which particular plugin would you recommend?

http://www.wordfence.com/ here. Implemented it ever since I started noticing these attacks.

Re: Huge attack on WordPress sites could spawn never-before-seen super botnet

#34
post #28
post #3

Rate-limiting login attempts out-of-the-box is something Wordpress should have included a LONG time ago. Maybe 1% of installs will setup the plugin to do this. No idea why they haven't added this yet.

Unfortunately it doesn't look like that would do any good here. With over 200k different botnet controlled machines, all that tracking the IP sources would do here is create massive blocklists. There's already evidance growing that the botnet is trying 2-3 passwords per source IP - effectively bypassing existing limiting plugins. A solution to the above is to limit the logins per account per timeframe, but that just…

Indeed a massive pain. I've been getting alerts from dreamhost regarding increased memory usage. I have http://www.wordfence.com/ installed and my blocklist only increases.

Re: Huge attack on WordPress sites could spawn never-before-seen super botnet

#35
It is time for every Wordpress user to consider to switch to Octopress. Static sites have no attack vector, don't need security updates and are faster out of the box. Octopress has importers for many blogging systems including Wordpress:

https://github.com/mojombo/jekyll/wiki/blog-migrations

P.S.: I have migrated a few days ago myself from Posterous to Octopress. It was a piece of cake.

Re: Huge attack on WordPress sites could spawn never-before-seen super botnet

#36
post #35

It is time for every Wordpress user to consider to switch to Octopress. Static sites have no attack vector, don't need security updates and are faster out of the box. Octopress has importers for many blogging systems including Wordpress: https://github.com/mojombo/jekyll/wiki/blog-migrations P.S.: I have migrated a few days ago myself from Posterous to Octopress. It was a piece of cake.

I am prepared to bet folding money that only software-sy types like us consider this a viable option. For everyone else it will seem like an unnecessary complication.

Re: Huge attack on WordPress sites could spawn never-before-seen super botnet

#38
post #35

It is time for every Wordpress user to consider to switch to Octopress. Static sites have no attack vector, don't need security updates and are faster out of the box. Octopress has importers for many blogging systems including Wordpress: https://github.com/mojombo/jekyll/wiki/blog-migrations P.S.: I have migrated a few days ago myself from Posterous to Octopress. It was a piece of cake.

Static site generators require a lot of sacrifices:

What about non-technical users? Multi-author blogs? Idiot-proof extensibility? Updates from phones and tablets? Huge sites with thousands of posts? Editorial and review systems? Access to thousands of cheap or free themes?

The ideal static site user is in a pretty privileged group. Most WordPress users would be better off securing WordPress and using a caching plugin that gives them the benefits of a powerful, dynamic platform while serving static files with automatic serverside compilation: http://wordpress.org/extend/plugins/wp-super-cache/

Re: Huge attack on WordPress sites could spawn never-before-seen super botnet

#39
post #19

If you still have user id #1 and/or the user "admin" on your wordpress install, you just haven't been using wordpress long enough to know what bad ideas those are.

I've not heard of the problem of a user with id #1 before, can you explain please? What's the issue with a user id #1 when the username is not admin?

Re: Huge attack on WordPress sites could spawn never-before-seen super botnet

#40
post #8
post #5

I can confirm. We host a lot of WordPress blogs (for photographers) and our scans have have detected an uptick in installs infected with malicious files. I'm not sure if it's the same attack mentioned in the article but the last 2 weeks have been the worst I've seen. In my experience people get compromised due to bad folder permissions or old versions of WP. I hadn't considered brute-force password attacks.

I've lost count of how many times I've seen people chmod /wp-content/upload to 777. I blame laziness, stupid presets in "one-click" installations and silly how-to's found all over the web.

I was setting up a Wordpress site for someone once (I'm not really a web developer). I downloaded an image gallery plugin and installed it locally. Wouldn't work. I went to the instructions and found that it required wp-content/upload to be set to 777. I abandoned the plugin soon after. However, if I hadn't been running Linux for a year before that, I'd probably have just done it.

The difficulty with the democratisation of software and web development is that inevitably, people will make mistakes like this. The sad part is there's probably millions of articles explaining why this is a bad idea, but the people most at risk will never see them.

Post reply on HN