• We evidentially got smacked with the iFrame virus – but I have not seen where the code has been compromised.

    We do have two unusual .php files on the files list on the Theme Editor – but I can not find them in the actual filesystem.

    They have names of 7e30804b68501ac775c35e1db21b502f.php and 9cb702aa084691e66c789c1e98d6233a.php

    Any ideas what is happening here?

Viewing 13 replies - 1 through 13 (of 13 total)
  • I would start by deleting the files you’ve listed (via FTP) and running the Exploit Scanner plugin to see what else might have been compromised.

    Also, Hardening WordPress is a good starting point for WP security.

    Thread Starter sdickert

    (@sdickert)

    Sadly there are no files that match those names on the server which is why I summer I have been hit.

    I will try the plug in. Any other advice?

    I have the exact same two files and filenames myself, I was thinking it might be the timthumb.php vulnerability. I tried a grep on all files and cant find anything out of the ordinary and a quick search in the database for those filenames brings up nothing.

    Any ideas anyone? Theyre seemingly undeletable.

    Thread Starter sdickert

    (@sdickert)

    Funny – I have TimThumb as well.

    Thread Starter sdickert

    (@sdickert)

    I replaced the copy I had with the newest version from google code. Right now, I think we are having database problems.

    Did one of your files contain base64 code and the other the word “loch” any chance? Any luck finding any traces of it? Check your cache directory for timthumb in your theme folder too as I found those files there in one of my backups yet cant see them on the server via FTP.

    I certainly hope we are. Anyone have any more input on what to do?

    Okay now I have some improvement, go to your themes cache directory in cpanel or whatever control panel you are using, browse to wpcontent>themes>yourtheme>cache>

    Find the two (or more) php files, try control and F and search .php and you will see them, for some reason they were not showing at all in filezilla and nor were all the timthumb text files.

    PartyOn – thank you! I found one of the files hidden in wp-feeds.php in my theme cache. Started with eval(gzinflate(base64_decode and just went on and on. I deleted it. Now I just searched on the specific php 9cb702aa084691e66c789c1e98d6233a.php that was showing up in my blog editor and found a bunch of TimThumb files in my ftp, but not sure if I am supposed to delete those too? I am a newbie at this! Thanks for the help!!

    Hey thank you too, I didnt even notice that file had been added or modified, does anyone know if that file is meant to be there and has been modified maliciously or should it simply not be there? I have deleted it now though.

    I would delete them as well as theyre not part of your theme at all and are just as bad as the feeds file.

    I am EXTREMELY new here (less than 5 minutes!) and saw this strange file in the control panel:

    9cb702aa084691e66c789c1e98d6233a.php with content “loch”

    A few weeks back the TimThumb plugin apparently opened the site to a virus, and I quickly updated the TimThumb file with updated code.

    Is the weird file above going to open the site up to viruses again? If so, what is the best way to remove it? PLEASE HELP!

    This topic has been covered before, but I’ll post a fresh response.

    1. Delete your WordPress installation, including the wp-config.php. You do not need to delete your uploads. Those don’t seem to be affected but give your upload directories a good look through and make sure no funny files are in there (ie. upd.php is a common one)
    2. Delete your database user that has all permissions to the database connected to your WP account and create a new user with all permissions and a new password. KEEP YOUR OLD DATABASE – there hasn’t been reports of it being compromised.
    3. Upload a fresh squeezed WordPress files from WordPress.org including all the plugins and theme(s) you were using FROM WORDPRESS.ORG. If there was any plugin or theme not uploaded from WordPress.org, it’s at your own risk.
    4. Set up your wp-config.php file to login to your Old database using the New username and password
    5. Should be good to go

    Once you have completed that, DELETE THE CACHE ON YOUR BROWSER and happy WordPressing!!!

    Post more questions if I left out anything. But the key is do not keep anything but the DB and YOUR uploads from the previous install. Should take a couple of hours but when you’re done you’ll be fine.

    ONE LAST NOTE: DO NOT USE TIMTHUMB AND IF YOU DO, MAKE SURE IT’S CONFIGURED NOT TO BE ACCEPTING CRAP FROM A REMOTE SERVER…ONLY LOCALHOST STUFF SHOULD BE PERMITTED.

    Best wishes.

    I have the same php file… what to do? Some security risk?

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Strange PHP files in the template editor page – but not in filesystem’ is closed to new replies.