Get a fresh cup of coffee, take a deep breath and carefully follow this guide. When you’re done, you may want to implement some (if not all) of the recommended security measures.
If you’re unable to clean your site(s) successfully, there are reputable organizations that can clean your sites for you. Sucuri and Wordfence are a couple.
Thread Starter
shori
(@shori)
Thanks for the response.
Almost all of those things were done right after the incident. The sites were scanned and infected files deleted, backups were made of what remained, and the sites were hardened.
What I’m trying to do now is pick up the pieces that remain and use whatever I can of them. I prefer that to starting from scratch at rebuilding the sites.
My challenge is that I am not a WordPress techie, and do not know what is contained where, etc. I do know that files like index and htacces were corrupted, but I don’t know how to rewrite them to point at the remaining files, etc. it appears (to me) that most of my pages are still there. I just need to figure out how to make them appear.
A vanilla wordpress instalation will only have the following .htaccess rules:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
And the following in the root index.php file:
<?php
/**
* Front to the WordPress application. This file doesn't do anything, but loads
* wp-blog-header.php which does and tells WordPress to load the theme.
*
* @package WordPress
*/
/**
* Tells WordPress to load the WordPress theme and output it.
*
* @var bool
*/
define( 'WP_USE_THEMES', true );
/** Loads the WordPress Environment and Template */
require __DIR__ . '/wp-blog-header.php';
