As I type these words, there is an on-going and highly-distributed, global attack on WordPress installations across virtually every web host in existence. This attack is well organized and again very, very distributed; we have seen over 90,000 IP addresses involved in this attack.
At this moment, we highly recommend you log into any WordPress installation you have and change the password to something that meets the security requirements specified on the WordPress website. These requirements are fairly typical of a secure password: upper and lowercase letters, at least eight characters long, and including “special” characters (^%$#&@*).
You have now changed your WordPress password, correct? Good.
The main force of this attack began last week, then slightly died off, before picking back up again yesterday morning. No one knows when it will end. The symptoms of this attack are a very slow backend on your WordPress site, or an inability to log in. In some instances your site could even intermittently go down for short periods.
We are taking several steps to mitigate this attack throughout our server farm, but in the same breath it is true that in cases like this there is only so much that can actually be done. The servers most likely to experience service interruptions will be VPS and Dedicated servers hosting high numbers of WordPress installations, due to the incredibly high load this attack has been seen to cause.
If you are hosted on a VPS or Dedicated server and you would like for us to take a more severe, heavy-handed approach to mitigate this attack, we can do this via means such as password-protecting (via .htaccess) all wp-login.php files on the server. If you would like our assistance with this, please contact us via normal support channels.
Again, this is a global issue affecting all web hosts. Any further information we could provide at this moment would be purely speculation. Our hope is that this attack ends soon, but it is a reminder that we must all take account security very seriously.
WordPress Login – Brute Force Attack
There is a worldwide, highly-distributed WordPress attack that is ongoing. This attack is known to be using forged or spoofed IP addresses. We are actively blocking the most common attacking IP addresses across our server farm. The following steps can be used to secure (by password protection)
wp-login.php for all WordPress sites in your cPanel account:
How to Password Protect the wp-login.php File
There are two (2) steps in accomplishing this. First you need to define a password in the
.wpadmin file, and then you activate the security in the
Step 1: Create the Password File
Create a file named
.wpadmin and place it in your home directory, where visitors can’t access it. (Please note there is a period preceding the wpadmin in that file name.) The following example is for cPanel. Plesk would require placing the file in
(where “username” is the cPanel username for the account.)
Put the username and encrypted password inside the
.wpadmin file, using the format
(where “john” is a username of your choice, and the password shown is encrypted.)
Option A: Generate Password File & Uploading Via File Manager
One way to do this is to generate the file using the website linked below, and then upload it to your site via FTP or File Manager. In the directions below, we will use File Manager, but you could use FTP instead, for those of you familiar with FTP.
- Visit: http://www.htaccesstools.com/htpasswd-generator/
- Use the form to create the username and password.
- Login to cPanel in another window or tab.
- Click on File Manager.
- Select Home Directory.
- Check Show Hidden Files (dotfiles) if not already checked.
- Click on the Go button.
- Look for a
- If one exists, right click on it and select Code Edit to open the editor. Click on the Edit button to edit the file.
- If one does not exist, click on New File at the top of the page, and specify the name as
.wpadmin(with the dot at the front) and click on theCreate New File button.
- Paste the code provided from the website in step 2.
- Click on the Save Changes button when complete.
- You can Close the file when finished.
Option B: Creating the Password File via SSH / Command Line
To create the encrypted password you will need to use a utility such as the command-line program htpasswd. More detailed technical information about htpasswd can be found athttp://httpd.apache.org/docs/current/programs/htpasswd.html.
An example would be to do this:
You would then be prompted to enter the password you wish to use for the username “john” in order to access the wp-login page. You can then log into the wp-admin interface as you normally would. There are many other online tools that can be used to convert standard passwords to encrypted for this purpose.
Step 2: Update the .htaccess File
All domains under the home directory will share the common
.wpadmin file. (The command listed in Option B above creates the
/home/username/.wpadmin file due to the
The last step is to place the following code in the
ErrorDocument 401 "Unauthorized Access"
ErrorDocument 403 "Forbidden"
AuthName "Authorized Only"
Note: replace “username” above with your cPanel username.
If you require assistance securing your kimtown server, please contact our support department by opening a new ticket, and we can implement a solution for all domains on the server. Please note this would have to be removed manually once the attack has subsided.