WordPress runs 60% of the websites that use a CMS<\/strong> as their main engine. WordPress is a powerful tool<\/a>, there is no doubt about that.<\/p>\n\n\n\n However, the fact that WordPress is so well established in the digital world (and the mere fact that the vast majority of the world’s websites run on it) also makes it a tool that hackers frequently attack.<\/p>\n\n\n\n Although there are no computer systems, websites or any system that is infallible (just ask banks and large companies), WordPress is actually quite safe if we follow several rules that help to keep attacks under control.<\/p>\n\n\n\n There are several reasons why someone would want to gain access to the dashboard or server on which a website is running, but there are three main reasons for attacks:<\/p>\n\n\n\n For example by changing the payment addresses or API’s that we use to monetise our website.<\/p>\n\n\n\n We may realise that something is not right when, after several days without receiving income, we find that the API, the user or the bank account of our monetisation system have been changed.<\/p>\n\n\n\n If you are an e-commerce that sells online and a security breach steals your customers’ credit card numbers, for example, you will lose credibility and users’ trust in your site. If the data leakage is large and\/or very sensitive, you may even have legal problems.<\/p>\n\n\n\n Data from users’ sign-ups for example, of websites that monetise their newsletters and need the user to register (so people introduce names, personal data, language, email address\u2026) are a very juicy morsel in the form of a database that is worth the effort.<\/p>\n\n\n\n Google penalises websites that do not work properly or that violate the content and quality guidelines<\/a> set by the company.<\/p>\n\n\n\n You can play dirty against a competitor by fraudulently gaining access to that competitor’s website to abuse the site by adding spam links, creating low quality pages or deleting URL’s on a massive scale <\/strong>that will end up flooding the site with 404 errors with the strategy of making Google believe that it is a junk site.<\/p>\n\n\n\n If the mess is not fixed in time, Google will penalise the website, the website will drop in the SERPS, it will lose visibility and the attacking company will have one less competitor.<\/p>\n\n\n\n Although WordPress does its best to prevent our website from being sent to the graveyard, we can also do our part to make things difficult for those who want to do so.<\/p>\n\n\n\n If you want to avoid any unpleasant surprises and troubles by seeing your WordPress hacked, get down to work with the following tasks that I mention below.<\/p>\n\n\n\n A password is not secure because it is longer or has more or less characters, but because it is a combination of both.<\/p>\n\n\n\n Given the data processing capacity of today’s computers (about 8 billion calculations per second) a password can only be considered secure against brute force attacks (down you will read about it) if it has more than 20 characters<\/strong> and includes lowercase letters, uppercase letters, numbers, special symbols and all of these are combined randomly.<\/p>\n\n\n\n In this post I explain how to design strong and secure passwords<\/a> and how to manage a large number of unmemorable passwords without going crazy or having to write them down in an excel spreadsheet.<\/p>\n\n\n\n Exactly: Spending time generating good passwords and then pasting them into an excel sheet? Doesn’t sound like a good idea.<\/p>\n\n\n\n Updates are not mere whims designed to add more functionality to a theme or plugin. They also fix security holes that can compromise the stability of a website.<\/p>\n\n\n\n Having our WordPress, theme and plugins outdated means earning odds of having an unstable site that is more prone to attacks.<\/p>\n\n\n\n The default login address for every WordPress site in the world is websitename.com\/wp-admin<\/span> o \/wp-login<\/span>. \nSo if you know that a website is a WordPress you can check if the administrators have changed that login address by adding \/wp-admin or \/wp-login to the initial URL*. <\/p>\n\n\n\n *You can check if a website works with WordPress in less than a minute by analysing its source code or pasting the URL in a tool like\u00a0WhatCMS<\/a>)<\/em>\u00a0<\/p>\n\n\n\n By the way: as you can see the access address to my website is not \/wp-admin but another one<\/em> By changing the default login address of our WordPress we directly avoid the so-called brute force attacks (randomly testing passwords), as we will see in the next section.<\/p>\n\n\n\n To change the WordPress login address quickly and easily I use a very light and effective plugin: WPS Hide Login<\/a>. <\/p>\n<\/div>\n\n\n\n <\/p>\n<\/div>\n<\/div>\n\n\n\n To change the default login address using WPS Hide Login simply enter the URL you want to use as your login address and tell the plugin what you want to happen when someone wants to access the default login address.<\/p>\n\n\n\n If you forget the login address you set, you will have to deactivate the plugin through the server files and the default WordPress login address will be set again.<\/strong><\/p>\n\n\n\n Brute-force attacks are trial-and-error attacks: randomly trying out passwords<\/strong> until one of them is correct. If the password is weak, we are gaining points for attackers to gain access to our website.<\/p>\n\n\n\n If we have not changed the default access address of our WordPress, as we explained in the previous section, attackers should only point their bots to the access page of our WordPress and program them to test passwords randomly and uninterruptedly.<\/p>\n\n\n\n But there are ways to avoid that someone could be testing passwords without pause: anti-brute force systems.<\/p>\n\n\n\n There are lightweight and effective plugins that block an ip address when it exceeds the number of access attempts you have specified.<\/p>\n\n\n\n I use either Loginizer <\/a> or WPS Limit Login<\/a> (same developers as WPS Hide Login).<\/p>\n\n\n\n Install one of these systems, program it correctly and you’re done.<\/p>\n\n\n\n As you can see in the image above, on average there are one or two login attempts using a random password every 10 minutes or so (and I’ve seen websites with much worse records than this one). The bots attack the default WordPress login URLs (and they also know which is the admin user, easy to get through the author id), which means that if we change that login URL we will avoid these attacks.<\/p>\n\n\n\n In my experience all the WordPress I’ve worked with (ALL of them) are attacked by brute force systems. In other words: whenever I’ve set up a system to log brute force attacks I’ve always ended up getting instant data.<\/strong> If you want to go more pro and have a bomb-proof WordPress you can combine all of the above with a Two Factor Authentication (2FA) system.<\/p>\n\n\n\n A 2FA system is the same as what a bank does to confirm a bank transfer: it asks you for your card number and also asks you for the code that was just sent to you by SMS.<\/p>\n\n\n\n To put it all in a nutshell, the ingredients for an insecure website are the following:<\/p>\n\n\n\n Use a lame password, or worse, use the same lame password for everything.<\/strong><\/p>\n<\/div>\n\n\n\n Not having our WordPress, themes and plugins properly updated to the latest version<\/strong><\/p>\n<\/div>\n<\/div>\n\n\n\n Not changing the default login address of WordPress<\/strong><\/p>\n<\/div>\n\n\n\n Not having a brute force attack rejection system in place<\/strong><\/p>\n<\/div>\n<\/div>\n\n\n\n If our website has been hacked and we notice it early on, we must undo all the changes the attackers have made to the systems. However, that can be hard work and often impossible. That is why it is extremely important to work with competent hosting providers<\/strong> who can lend a hand when things go wrong.<\/p>\n\n\n\n I mainly work with Loading.es, for the simple reason that they offer an efficient and very fast customer support system, a user-friendly server management environment and a high-quality backup policy.<\/p>\n\n\n\n
\n\n\n\nReasons why someone would want to attack our website<\/h2>\n\n\n\n
![\"logo](\"https:\/\/spagenciaseo.com\/wp-content\/uploads\/2020\/04\/hacker.png\")
<\/figure><\/div>\n\n\n\nTo get money<\/h3>\n\n\n\n
To obtain data<\/h3>\n\n\n\n
To elliminate competition<\/h3>\n\n\n\n
\n\n\n\nProtect your WordPress from attacks<\/h2>\n\n\n\n
Choose a good password<\/h3>\n\n\n\n
![\"c\u00f3mo](\"https:\/\/spagenciaseo.com\/wp-content\/uploads\/2020\/04\/contrasenas-buenas-wordpress.jpg\")
<\/figure><\/div>\n\n\n\n
\n\n\n\nKeep the website updated<\/h3>\n\n\n\n
\n\n\n\nChange your WordPress login address<\/h3>\n\n\n\n
\ud83d\ude09<\/p>\n\n\n\n![\"\"](\"https:\/\/spagenciaseo.com\/wp-content\/uploads\/2020\/04\/wps-hide-login-logo.png\"){kind=logo}
<\/figure><\/div>\n\n\n\n![\"\"](\"https:\/\/spagenciaseo.com\/wp-content\/uploads\/2020\/04\/wps-hide-login-snapshot.jpg\")
<\/figure><\/div>\n\n\n\n
\n\n\n\nAvoid brute force attacks<\/h3>\n\n\n\n
Plugins to prevent brute force attacks<\/h4>\n\n\n\n
![\"\"](\"https:\/\/spagenciaseo.com\/wp-content\/uploads\/2020\/04\/loginizer-logo.png\"){kind=logo}
![\"\"](\"https:\/\/spagenciaseo.com\/wp-content\/uploads\/2020\/04\/wps-limit-login-logo.jpg\"){kind=logo}
![\"\"](\"https:\/\/spagenciaseo.com\/wp-content\/uploads\/2020\/04\/loginizer-brute-force-attempts.jpg\")
So yes: your WordPress is probably also suffering from an automated system that is testing passwords at this very moment.<\/p>\n\n\n\n
\n\n\n\nImplement a two-step authentication system (TFA)<\/h3>\n\n\n\n
The summary of what NOT to do<\/h3>\n\n\n\n
\n\n\n\nFixing a disaster<\/h2>\n\n\n\n
![\"\"](\"https:\/\/spagenciaseo.com\/wp-content\/uploads\/2020\/04\/banner_loading-es150x200_2.png\")
<\/a><\/figure><\/div>\n<\/div>\n<\/div>\n\n\n\n![\"\"](\"https:\/\/spagenciaseo.com\/wp-content\/uploads\/2020\/04\/copias-seguridad-disponibles.jpg\")