Suffering a hack can be one of the more frustrating experiences you’ll have on your online journey. Like most things however, taking a pragmatic approach can help you maintain your sanity. While also moving beyond the issues with as little impact as possible.<\/p>\n\n\n\n
A hack is a very ambiguous term, which in it of itself will provide little insights into what exactly happened. To ensure you get the help you need via the forums, be sure to understand the specific symptoms that lead you to believe you’ve been hacked. These are otherwise known as Indicators of Compromise (IoC).<\/p>\n\n\n\n
A couple of IoC’s that are clear indicators of a hack include:<\/p>\n\n\n\n
Not all hacks are created equal, so when engaging in the forums please keep this in mind. If you can better understand the symptoms the teams will be better equipped to provide help.<\/p>\n\n\n\n
Below you will find a series of steps that are designed to help you start working through the post-hack process. They are not all encompassing as it would be impractical to account for every scenario, but they are designed to help you think through the process.<\/p>\n\n\n\n
Stay calm.<\/strong><\/p>\n\n\n\n When addressing a security issue, as a website owner, you’re likely experiencing an undue amount of stress. It’s often the most vulnerable you have found yourself since being on line and it’s contrary to what every one told you, “Hey, WordPress is Easy!!”<\/p>\n\n\n\n The good news is that all is not lost! Yes, you might lose some money. Yes, you might take a hit against your brand. Yes, you will recover from this.<\/p>\n\n\n\n So, yes, take a step back and compose yourself. Doing so will allow you to more effectively take control of the situation and allow you to recover your online presence.<\/p>\n\n\n\n Document.<\/strong><\/p>\n\n\n\n The first actionable step you should take post-compromise is documentation. Take a moment to document what you’re experiencing, and if possible times. A couple of things you want to keep in mind:<\/p>\n\n\n\n You are creating the baseline for what is recognized as an incident report. Whether you are planning to perform the incident response yourself, or engage a professional organization, this document will prove invaluable over time.<\/p>\n\n\n\n Recommend taking a moment to annotate details of your host environment as well. It will be required at some point during the incident response process.<\/p>\n\n\n\n Scan your website.<\/strong><\/p>\n\n\n\n When scanning your website you have a few different ways to do this, you can use external remote scanners or application level scanners. Each are designed to look and report on different things. No one solution is the best approach, but together you improve your odds greatly.<\/p>\n\n\n\n Application Based Scanners (Plugins):<\/p>\n\n\n\n Remote Based Scanners (Crawlers):<\/p>\n\n\n\n There are also a number of other related security plugins<\/a> available in the WP repo. The ones annotated above have been around a long time and have strong communities behind each of them.<\/p>\n\n\n\n Scan your local environment.<\/strong><\/p>\n\n\n\n In addition to scanning your website, you should start scanning your local environment. In many instances, the source of the attack \/ infection begins on your local box (i.e., notebook, desktop, etc…). Attackers are running trojans locally that allow them to sniff login access information to things like FTP and \/wp-admin that allow them to log in as the site owner.<\/p>\n\n\n\n Make sure you run a full anti-virus\/malware scan on your local machine. Some viruses are good at detecting AV software and hiding from them. So maybe try a different one. This advice extends to both Windows, OS X and Linux machines.<\/p>\n\n\n\n Check with your hosting provider.<\/strong><\/p>\n\n\n\n The hack may have affected more than just your site, especially if you are using shared hosting. It is worth checking with your hosting provider in case they are taking steps or need to. Your hosting provider might also be able to confirm if a hack is an actual hack or a loss of service, for example.<\/p>\n\n\n\n One very serious implication of a hack these days is around Email blacklisting. This seems to be happening more and more. As websites are abused to send out SPAM emails, Email Blacklist authorities are flagging the website IP’s and those IP’s are often associated with the same server being used for email. The best thing you can do is look at Email providers like Google Apps<\/a> when it comes to your business needs.<\/p>\n\n\n\n Be Mindful of Website Blacklists.<\/strong><\/p>\n\n\n\n Google Blacklist<\/a> issues can be detrimental to your brand. They currently blacklist somewhere in the neighborhood of 9,500 to 10,000 websites a day. This number grows daily. There are various forms of warnings, from large splash pages warning users to stay away, to more subtle warnings that pop up in your Search Engine Result Pages (SERPs).<\/p>\n\n\n\n Although Google is one of the more prominent ones, there are a number of other blacklist entities like Bing, Yahoo and a wide range of Desktop AntiVirus applications. Understand that your clients \/ website visitors may leverage any number of tools and any one of them could be causing the issue.<\/p>\n\n\n\n It’s recommended that you register your site with the various online webmaster consoles like:<\/p>\n\n\n\n Improve your Access Controls.<\/strong><\/p>\n\n\n\n You will often hear folks talking about updating things like Passwords. Yes, this is a very important piece, but it’s one small piece in a much larger problem. We need improve our overall posture when it comes to access control. This means using Complex, Long and Unique passwords for starters. The best recommendation is to use a Password Generator like those found in apps like 1Password<\/a> and LastPass<\/a>.<\/p>\n\n\n\n Remember that this includes changing all access points. When we say access points we mean things like FTP \/ SFTP, WP-ADMIN, CPANEL (or any other administrator panel you use with your host) and MYSQL.<\/p>\n\n\n\n This also extends beyond your user, and must include all users that have access to the environment.<\/p>\n\n\n\n It is also recommended to consider using some form of Two Factor \/ Multi-Factor authentication system<\/a>. In it’s most basic form, it introduces, and requires, a second form of authentication when logging into your WordPress instance.<\/p>\n\n\n\n Some of the plugins available to assist you with this include:<\/p>\n\n\n\n Reset all Access. <\/strong><\/p>\n\n\n\n Once you identify a hack, one of the first steps you will want to do is lock things down so that you can minimize any additional changes. The first place to start is with your users. You can do this by forcing a global password reset for all users, especially administrators.<\/p>\n\n\n\n Here is a plugin that can assist with this step:<\/p>\n\n\n\n You also want to clear any users that might be actively logged into WordPress. You do this by updating the secret keys in wp-config. You will need to create a new set here: the WordPress key generator<\/a>. Take those values then overwrite the values in your wp-config.php file<\/a> with the new ones. This will force anyone that might still be logged in off.<\/p>\n\n\n\n Create a Backup.<\/strong><\/p>\n\n\n\n You hopefully have a backup of your website, but if you don’t, this will be a good time to create one<\/a>. Backups are a critical piece of your continuation of operations, and should be something you actively plan for moving forward. You should also ask your host what their policy is as it pertains to backups. If you do have a backup, you should be able to perform a restore and skill right into the forensics work.<\/p>\n\n\n\n Side note: It’s important you keep regular backups of your database<\/a> and files<\/a>. If this ever happens again.<\/p>\n\n\n\n Regardless, before you move into the next phase of cleaning, it is recommended you take one more snapshot of the environment. Even if it’s infected, depending on the type of hack, the impacts can cause a lot of issues and in the event of catastrophic failure you’ll at least have that bad copy to reference.<\/p>\n\n\n\n Find and remove the hack.<\/strong><\/p>\n\n\n\n This will be the most daunting part of the entire process. Finding and removing the hack. The exact steps you take will be dictated by a number of factors, including, but not limited to, the symptoms provided above. How you approach the problem will be determined by your own technical aptitude working with websites and web servers.<\/p>\n\n\n\n To help in the process though, we’ve included a number of different resources that should help you in the process:<\/p>\n\n\n\n It might be tempting to purge everything and start over. In some cases that’s possible, but in many instances it’s just not possible. What you can do however is reinstall certain elements of the site with little regard to impacting the core of your website. You always want to make sure you reinstall the same version of software your website is using, if you choose an older or newer one you’re likely to kill your website. When reinstalling, be sure not to use the reinstall options in your WP-ADMIN. Use your FTP \/ SFTP application to drag and drop the versions. This will prove much more effective in the long run as those installers often only overwrite existing files, and hacks often introduce new files… You can replace the following directories safely:<\/p>\n\n\n\n From there, it’s recommended that you be more diligent in updating and replacing files as you move through wp-content as it contains your theme and plugin files.<\/p>\n\n\n\n The one file you will definitely want to look at is your .htaccess file. It’s one of the more common files, regardless of the type of infection, that is most often updated and used for nefarious activities. This file is often located at the root of your installation folder, but can also be embedded within several other directories on the same installation.<\/p>\n\n\n\n Regardless of the type of infection, there are will be some common files you will want to keep an eye on during your remediation process. They include:<\/p>\n\n\n\n If modified, these files can usually adversely affect all page requests, making them high targets for bad actors.<\/p>\n\n\n\n Leverage the Community<\/strong><\/p>\n\n\n\n We often forget but we’re a community based platform, this means that if you’re in trouble someone in the community is likely to give a lending hand. A very good place to start if you’re strapped for cash or just looking for a helping hand is the WordPress.org Hacked<\/a> or Malware<\/a> forum.<\/p>\n\n\n\n Update!<\/strong><\/p>\n\n\n\n Once you are clean, you should update your WordPress installation<\/a> to the latest software<\/a>. Older versions are more prone to hacks than newer versions.<\/p>\n\n\n\n Change the passwords again!<\/strong><\/p>\n\n\n\n Remember, you need to change the passwords for your site after<\/em> making sure your site is clean. So if you only changed them when you discovered the hack, change them again now<\/a>. Again remembering to use Complex, Long and Unique passwords.<\/p>\n\n\n\n You may consider to change the database user account and password. When you changed them, do not forget enhancing them to wp-config.php file.<\/p>\n\n\n\n Forensics.<\/strong><\/p>\n\n\n\n Forensics is the process of understanding what happened. How did the attackers get in? The goal is to understand the attack vector a bad actor used to ensure they’re unable to abuse it again. In many instances, it’s very difficult for website owners to perform this type of analysis due to lack of technical knowledge and \/ or available data. If you do have the metadata required, then there are tools like like OSSEC<\/a> and splunk<\/a> that can help you synthesize the data.<\/p>\n\n\n\n Secure your site.<\/strong><\/p>\n\n\n\n Now that you have successfully recovered your site, secure it by implementing some (if not all) of the recommended security measures<\/a>.<\/p>\n\n\n\n Can’t Log Into WordPress Admin Panel<\/strong><\/p>\n\n\n\n There are times that a bad actor will hijack your administrator account[s]. This is not a reason to panic, there are a few different things you can do to regain control of your account. You can follow these steps to reset your password<\/a><\/p>\n\n\n\n Tools like phpMyAdmin<\/a> and Adminer<\/a> are often made available via your hosting provider. They allow you to log into your database directly, bypassing your Administration Screen<\/a> and resetting your user in the users table If you don’t want to mess with password hashes or can’t figure it out, simply update your email and go back to Login Screen, click forgot password, and wait for the email.<\/p>\n\n\n\n Using version control?<\/strong><\/p>\n\n\n\n If you are using version control, it can be very handy to quickly identify what has changed and to rollback to a previous version of the website. From the terminal or command line you can compare your files with the versions stored in the official WordPress repository.<\/p>\n\n\n\n $ Or compare a specific file:<\/p>\n\n\n\n $ Help I think I’ve been hacked Suffering a hack can be one of the more frustrating experiences you’ll have on your online journey. Like most things however, taking a pragmatic approach can help you maintain your sanity. While also moving beyond the issues with as little impact as possible. A hack is a very ambiguous […]<\/p>\n","protected":false},"featured_media":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","category":[77,74],"class_list":["post-10821282","helphub_article","type-helphub_article","status-publish","hentry","category-faqs","category-wordpress-overview"],"revision_note":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/documentation\/wp-json\/wp\/v2\/articles\/10821282","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/documentation\/wp-json\/wp\/v2\/articles"}],"about":[{"href":"https:\/\/wordpress.org\/documentation\/wp-json\/wp\/v2\/types\/helphub_article"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/documentation\/wp-json\/wp\/v2\/comments?post=10821282"}],"version-history":[{"count":1,"href":"https:\/\/wordpress.org\/documentation\/wp-json\/wp\/v2\/articles\/10821282\/revisions"}],"predecessor-version":[{"id":16355188,"href":"https:\/\/wordpress.org\/documentation\/wp-json\/wp\/v2\/articles\/10821282\/revisions\/16355188"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/documentation\/wp-json\/wp\/v2\/media?parent=10821282"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.org\/documentation\/wp-json\/wp\/v2\/category?post=10821282"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}wp_users<\/code>.<\/p>\n\n\n\n svn diff .<\/code><\/p>\n\n\n\n svn diff \/path\/to\/filename<\/code><\/p>\n\n\n\nOther Resources<\/h2>\n\n\n\n