abletec

Hello, bhavyacolumbuz, & welcome. I’m not certain that what I’m going to say is gospel truth, but I will say these are fairly classic signs of a site compromise.

You may wish to check w/your host to see if they have a backup of the database from a couple days ago–maybe yesterday might not even be too late if it was working then. You may also want to check the trash to see if your posts may be there. Having said that, though, repairing the site isn’t much use unless you also kick the bad guys out.

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. It does no good to change credentials, etc., which you will need to do, if malware phones them 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 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.

Never log onto your site using a public 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 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. 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. 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.

Hello, luminarycrush. I didn’t mean to bail on you–however, right around the time we were doing this, our newest (& only) grandaughter arrived. Things got pretty hectic, as you might well imagine, & not hearing anything, I thought you’d resolved this. Evidently not. Apologies.

Ok, so let’s start again. Your permissions should be 0755 for files & 0644 for directories, generally speaking.

Your Apache user may not actually be an FTP user, & you should check for that.

You might wish to check this:
https://codex.ww.wp.xz.cn/Changing_File_Permissions

How are you running PHP, ie, fast_cgi, as an Apache module, etc?

Can we please see your Apache conf file? & what, if anything, are your error logs saying?

Please paste your .htaccess file into this reply, rcarp13. You can enclose it in backticks (), like this:

 line 1
line 2

If your .htaccess file is getting changed w/o your doing so, rcarp13, then we have to seriously look at the possibility that your site has been compromised.

What you uploaded to Pastebin is not a .htaccess file, please believe me.

Let’s have a look at your .htaccess again, rcarp13. I admit to being pretty surprised by that last 1.

What are the url’s in your dashboard settings?

I apologize, rcarp13. I inadvertently missed a line while I was copying & pasting. It should rather look like this:
<IfModule mod_rewrite.c>
# Begin WordPress
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
#End WordPress
</IfModule>

Again, I sincerely apologize for my cut-&-paste error. I thought something looked weird about it, but couldn’t quite figure it out till I went & did something else & then came back to look at it again.

Well, when I type in typetwodiabetes.us it is now redirecting to wp-admin/install.php. Please delete the wp-config.php file you put in the wp-admin folder.

Please open your wp-config.php file in your hosting control panel file manager or via FTP (preferably secure FTP) & change wp_debug from ‘false’ to ‘true’. Then try logging in & copy any errors displayed.

Please also let us see your .htaccess file.