18 April 2013 | 6,687 views

Large Scale Botnet Brute Force Password Cracking Against WordPress Sites

Check For Vulnerabilities with Acunetix

There have always been a lot of brute force attempts/bot scans and hacking attempts on WordPress hosted sites (due to flaws in the core and a multitude of insecure plugins) – this site being no exception (they’ve even done some minor damage before).

But things appear to have really ramped up recently with a large increase in brute force attacks on WordPress sites. It seems to be the work of a rather crude botnet, which hits up the normal admin username (along with a few others like test/root etc) with a bunch of common passwords. Once it gets in, it leaves a backdoor and adss itself to the botnet – and starts scanning for other victims.

Sucuri have confirmed that the number of brute force attacks in April is double than that of previous months in their blog post here – Mass WordPress Brute Force Attacks? – Myth or Reality

Hosting providers are reporting a major upsurge in attempts to hack into blogs and content management systems late last week, with WordPress installations bearing the brunt of the hackers’ offensive.

WordPress installations across the world were hit by a brute force botnet attack, featuring attempts to hack into installations using a combination of popular usernames (eg, “admin” and “user”) and an array of common passwords. Attacks of this type are commonplace; it is the sharp rise in volume late last week to around three times the normal volume rather than anything technically cunning or devious that has set alarm bells ringing.

The primary target appears to be WordPress installations but Joomla users also reportedly took a bit of a hammering.

Early suggestions are that hackers are looking to harvest “low-hanging fruit” as quickly as possible in order to gain access to a bank of compromised sites for follow-up malfeasance, which could be anything from hosting malware to publishing phishing pages or running some sort of denial of service attack. “It’s doorknob rattling, but on an industrial and international scale,” notes Paul Ducklin, Sophos’s head of technology for Asia Pacific.

This is a large scale attack though, well organized and very well distributed with over 90,000 IP addresses involved. So using something like the WordPress plugin Limit Login Attempts wouldn’t help much – as they are not sending many login requests from each IP address.

Cloudflare have already pushed out a block for this type of attack, both for paying and free customers – so if you’re using that you should be safe. (Patching the Internet in Realtime: Fixing the Current WordPress Brute Force Attack)

If you notice your admin login or blog in general is very sluggish, you might have already been hacked. The outgoing brute force attempts take a lot of server resources.

WordPress founder Matt Mullenweg said that the attack illustrates the need to use a distinct username and a hard-to-guess password, common-sense advice that applies to using web services in general, not just for blog administration.

Olli-Pekka Niemi, vulnerability expert at security biz Stonesoft, outlined the range of possible motives behind the attack.

“A concern of this attack is that by compromising WordPress blogs attackers may be able to upload malicious content and embed this into the blog,” Niemi said. “When readers visit the blogs in question they would be then be subject to attack, come under compromise and develop into botnets. The attacks against the word press blogs seem to be distributed, with automated attacks coming from multiple sources.”

Matt Middleton-Leal, UK & Ireland regional director of corporate security dashboard firm Cyber-Ark, said hacks on corporate blogs might be used as an access point to hack into other (more sensitive) enterprise systems. Weak passwords need to be changed pronto, he argues.

“Common usernames and weak passwords are extremely risky online, however, the dangers are compounded if users re-use the same login credentials for other sites. Once the bad guys have cracked a username and password, it’s extremely common that they’ll attempt to use the same combination for additional sites in the attempt to fraudulently use accounts, or access information such as credit card details or corporate data.

“If WordPress users have been targeted in this attack, they should immediately seek to change their username and password details for their WordPress account, but also for any other accounts for which they use the same credentials,” he added.

There’s not a lot of info going around on what happens after a site has been compromised, in technical terms anyway – so I can’t really comment on that. But if you have decent file permissions, a strong password, you have already deleted the admin user long ago you should be safe.

If you want to add another level, just htpasswd protect your wp-admin directory. That will stop this (and any other similar attacks) dead in it’s tracks.

Stay safe fellow WordPress users.

Source: The Register



Recent in Password Cracking:
- ParanoiDF – PDF Analysis & Password Cracking Tool
- Source Code Hosting Service Code Spaces Deleted By Hacker
- Moscrack – Cluster Cracking Tool For WPA Keys

Related Posts:
- LCP – A Good FREE Alternative to L0phtcrack (LC5)
- Patator – Multi Purpose Brute Forcing Tool
- PACK – Password Analysis & Cracking Kit

Most Read in Password Cracking:
- Brutus Password Cracker – Download brutus-aet2.zip AET2 - 1,059,379 views
- Password Cracking Wordlists and Tools for Brute Forcing - 498,815 views
- Password Cracking with Rainbowcrack and Rainbow Tables - 414,170 views

Advertise on Darknet

One Response to “Large Scale Botnet Brute Force Password Cracking Against WordPress Sites”

  1. Frank Steiner 26 April 2013 at 12:50 pm Permalink

    It’s more important than ever to protect WordPress websites, or else there’s the chance that they could even be turned into used for criminal activities.

    I already had security measures in place to prevent brute force penetration but after seeing more than 10K tries to login into my blog in recent days I decided that whether or not they failed it wouldn’t cause pain having even tighter security.

    Now there is a Google Authenticator Plugin for WordPress. You could enable (or disable) it per user (admin, editor, etc). This plugin along with strong password is the best you can do to secure the back end. This is the plugin I installed for my personal website.