WordPress Security Experience - Bandwidth Lesson

Genesis

Administrator
Staff member
So in July this year I created a WordPress Website. All went well until end of August when its bandwidth nearly hit the roof. I thought I'd been Ddosed and deleted the Website after I'd made a backup to be recreated when I had some time again.

About two weeks ago I finally had time to recreate the Website at Gigarank. This time round I took several security precautions. When I created my "Admin" account I deliberately used a non-admin name. I also used the password generator to get a 100% password. And then after plenty of research loaded the WordFence Security plugin, and what a great experience that has been. What I like about WordFence is that it informs you of what has happened after a security event has taken place. I.e. script kids using scripts to force their way in. Here's an e-mail from Wordfence after such an event:

A user with IP address 125.77.238.162 has been locked out from the signing in or using the password recovery form for the following reason: Exceeded the maximum number of login failures which is: 10. The last username they tried to sign in with was: 'admin'
User IP: 125.77.238.162

I received a few of those e-mails and the IPs were all from China.

Next I was wondering whether I should do a country block, but soon learned that that would create BIG problems, as it would slow down the Website. Not a good solution. WordFence was great at picking up the bruteforce attempts, but then after doing some research found some additional protection for bruteforce attempts - BruteProtect Plugin. Reviews looked good. Will see how it goes.

At any rate, at least I learned a bandwidth lesson as well. Those unprotected and unblocked brute force attacks eat bandwidth and can easily lead to exhausting one's bandwidth on a shared server. And possibly suspension. So security like Wordfence and BruteProtect aren't a luxury, but a necessity for people with WordPress Websites.
 

ogah

New member
i use manual trick.
rename wp-login.php to other, then create a new wp-login.php with fake form :)
 

Genesis

Administrator
Staff member
I've just read somewhere about a trick as well about using Java to create a form input field that would not be visible to bots. Got some drawbacks, but yes, there are plenty of tricks out there. Good to hear about them. :smile:
 

Peter

Member
I get a few 404 requests on wp-login.php each month even though Wordpress have never been installed. :dodgy:
 

Genesis

Administrator
Staff member
Peter said:
I get a few 404 requests on wp-login.php each month even though Wordpress have never been installed. :dodgy:
Wow, have you worked out how that happens? :huh:
 

xdude

New member
probably because some script which scan for Wordpress login pages scanning his site. If the script get a positive result it save the url so another script would try brute forcing. If it get a 404 then it moves on. It's quite common thing.

I have an fully managed vps which has been having a brute force attack for 2 years. I was worried for a while but then got used to it. If you have solid security measures brute force never gonna work. This brute force is not a simple script kid type. It comes from IP addresses all over the world and scan for various things from cPanel user logins, FTP user logins, Wordpress admin user logins etc. Firewall automatically block the IP after 3 failed tries. Only what pisses me is all those hundreds of mails I get from server about this.