My first step is but it helped me. I had a fantastic old fashion pity party. I cried and railed against the evil hackers (that where probably 13 and smarter then me.) And I did before I even started my site, what I should have done. And here is where I want you to start. Learn how to protect yourself until you get hacked. The attractive thing about fix hacked wordpress database and why so many of us recommend because it is easy to learn, it is. Unfortunately, that is also a detriment to the health of our sites. We need to learn how to put in a security fence.
There are ways to pull this off, and a lot of them involve copying and FTPing files, exporting and re-establishing databases and more. Some of them are very complicated, so it is imperative that you select the one that is right. Then you may want to check into using a plugin for WordPress backups, if visit our website you're not of the technical persuasion.
It represents a task that is essential while it's an odd term . We're not simply being obsessive-compulsive here: servers go down every day, despite their promises of 99.9% uptime, and if you've had this happen to you, you understand the fear is it can cause.
Now we're getting into matters specific to WordPress. You have to rename it to config.php and alter the document config-sample.php, when you install WordPress. You need to deploy the database facts there.
However, I recommend that you install the Login LockDown plugin instead of any.htaccess controls. From being allowed after three failed login attempts from a certain IP address for one hour, login requests will stop. You can get into your admin panel whilst away from your office, and yet you still have protection against hackers if you do so.