abletec

Yes. I always recommend that be done following a site compromise. I realize it’s a frickin hassle, but this way it ensures that all the files are both accounted for & that they’re all clean.

You say you have other sites. So is this a multisite or do you just have single installs of each?

Also, you know what, Zach? Please let’s do this for the halibut in order to simplify the diagnostic process.

Please rename your .htaccess to htaccess, ie, simply remove the prepended .
Then, please create a new .htaccess w/just the following lines:
# BEGIN WordPress
# The directives (lines) between BEGIN WordPress and END WordPress are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
AddHandler application/x-httpd-ea-php70 .php
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
RewriteEngine On
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*)$ https://%{SERVER_NAME}%{REQUEST_URI} [R=301,L]
& let’s see how we go. We can always reenable your caching once these issues are resolved.

Hey Zach, I just went to your site again & got a 502 bad gateway error. Does Bluehost allow you to view error logs in its control panel, or can you secure them from Bluehost support?

Hello, zach12ary, & welcome. I think the most helpful thing you could do right now is provide a link to your site so we can see what sort of errors you’re receiving.

As a hosting provider myself & someone who also specializes in fixing compromised sites, my intuition is that this is not actually a server issue but has something to do w/the compromise. Did you perchance change your dashboard, control panel, & database passwords? That is something you should consider doing approximately yesterday :). The reason is that most hackers leave a backdoor into your site. These passwords might be 1 way they get in.

At any rate, please let’s see a link, & then we can go from there.

Hello, 12sp, & welcome. I suspect that the url’s are incorrect. Could you please provide an example of urls to links that are missing? Hover over the link & copy what appears in your browser address bar

BTW, I just submitted a holiday for consideration on your site.

yojimbokame, please form your website url like this:
hxxp://www.yourwebsite.com where http://www.yourwebsite.com is a place holder for your real website name.

We can assist better if we have the link.

Are you running your own server or are you on shared hosting?

Hello, yojimbokame, & welcome. Unfortunately, it appears your site has been compromised, or, to put it another way, hacked. I am so sorry.

I will post on how to fix a hack here, but be warned it can get technically involved. Once you’ve followed the outlined steps & are you’re very sure all injected content has been removed, you’ll need to contact Google for a request for consideration review.

Please kind of use this post as a checklist, checking each off as you go. Please carefully understand both objectives, ie, to repair the site, & to get it back fully under your control, as a compromise indicates that it is not, & the bad guys are therefore free to do whatever they want, whenever they want. If there’s anything at all you don’t understand, please ask. It’s important. If you feel this is all too overwhelming, you can post a job at http://jobs.wordpress.net.

A resource you can go to is:
http://codex.ww.wp.xz.cn/FAQ_My_site_was_hacked

When dealing w/a site compromise, the objectives are twofold:
1) Fix the site; &
2) Fix backdoors that the hacker used to gain entrance into your site, so this hopefully will not happen again.

Most people place great emphasis on objective #1, but, in truth, the 2nd one is actually the most important, as, without it, your site will continue to be reinfected.

Here are the steps to take.

First, notify your host, as this might be a serverside hack as opposed to simply a site compromise. Also, if you’re on shared hosting, the hack has the potential to compromise the entire server. Additionally, you may wish to take the site offline, & your host can help you do this. They might not help you–then again, they might. You won’t know unless you notify them. If they say it’s not their responsibility, (& it really may not be), then please continue reading.

Second, scan any devices you will use to log onto your website for malware (malicious software like viruses, etc). It does no good to follow these steps if malware phones your credentials home to their command & control center. It’s actually better to do more than 1 scan, each using a different program, as no single malware scanner can detect everything.

Third, secure your network. Definitively use secure FTP (file transfer protocol) as opposed to regular FTP. The port used for secure FTP varies from host to host. Many use port 22, some 2222, while others use different ports altogether. Check their knowledge base or call their support. You can ask this question when you notify them of the compromise in the first step. You can use a client like Filezilla, which can do secure file transfers.

Never log onto your site using a public WiFi hotspot, such as those in hotels, cafes, etc. Make sure you’ve changed the default password, Ssid, (&, if applicable) the username on your router/modem. If you don’t use wireless, turn it off in your router’s options.

All these steps are required to ensure that no one can snoop your credentials, etc.

Now that the device you’ll use to fix your site, as well as your network, is secure, it’s time to direct your attention to actually fixing your site.

Next, please log into your website hosting provider’s control panel from a secure connection and change all passwords, including those to any databases you may have set up. This includes your control panel/FTP credentials & your WordPress database. Also, change your salt keys as per the instructions in wp-config.php to log out all users. Please make the passwords long, containing upper & lowercase letters, numbers, & punctuation.

Next, take a backup of your website’s files. Be certain to label it such that the label contains both the date you backed it up on, as well as the word “hacked”–we certainly don’t want you accidentally restoring this backup! This can be helpful, though, in terms of perhaps being able to determine how this occurred, though my feeling is that it likely did so because of an outdated site, weak passwords, or unmaintained 3rd-party plugins or themes on the site. Probably you should just back up your web root. Depending on your host, it might be called public_html, htdocs, www, or /. If you don’t wish to back up the entire root, then at least back up your uploads folder, as well as others that might contain content that can’t be replaced.

Please also back up your database as well. The article at
http://codex.ww.wp.xz.cn/Backing_Up_Your_Database
shows you how to do that, in case you need it. The section regarding phpMyadmin is likely the most relevant to your case. It’s going to be necessary to search that database file to see if any evidence of the hack exists there. That can be done by opening the file in a text editor. To start off with, consider searching for the words:

<script
<? php;
base64;
eval 

preg_replace
strrev

This is not an exhaustive list, nor is the presence of any of these words conclusive proof of a site compromise, though some are more suggestive than others.

You might also wish at this point to backup your WordPress content. To do that:
* Log into your WordPress dashboard.
* Go to ‘Tools > Export’.
* Choose to export all content.

While in your dashboard, go to ‘Users > All Users’ and delete any users there that you don’t recognize, especially administrators. A WordPress account should never contain the username ‘admin’. If yours does, make an administrative account that does not contain the word (don’t forget to use a very strong password), then delete the old admin username account.

Also be advised that sometimes supposed image files can contain code, so open all your image files, particularly in your uploads folders, to ensure they really are images & don’t contain code. Better yet, if you have the images on your machine, replace files in the uploads folders with them.

If you find nothing, either in your database or in your /uploads folders, then the next step is to delete, then completely reinstall WordPress, as well as any plugins or themes you were using. Simply reinstaling WordPress from the dashboard is not effective. I also advise creating an entirely new database w/a new user & password. You can then import your content into the newly reinstalled site.

Please also let someone knowledgeable look at your .htaccess file so they can make certain no backdoor code exists there.

In summary, here are the steps:
1) Back up your WordPress files, including core, themes, & plugins;
2) Back up your database using PhpMyadmin;
3) Look through the database to insure there is no evidence of the hack;
4) Search the uploads folders for image files that contain code;
5) Let someone knowledgeable look at your .htaccess file.
6) If you have doubts about your database, please have a professional take a look.

It would also be helpful to install a plugin like Sucuri or Wordfence to scan for the compromised files.

I’m just really having difficulty figuring out exactly what your site is running, Nathan12. It actually seems like there might be a combination of technologies, ie, your file manager does show a WordPress folder, the packing portion shows a Revslider plugin, which tends to be associated w/WordPress, but, if it is a WordPress install, it’s very nonstandard. The homepage seems to be standard HTML.

I am also having considerable difficulties w/the screenshots provided, unfortunately.

You do have an option called “my installs”. Is anything there, perchance? That might help.