Certified Hosting/Naked Hosting Malware on Blogs: FUCK
 

2nd time around getting malware placed on my sites with certified/naked hosting. Unreal. Why offer hosting if your servers don't support a secure environment. Same .cc malware on Wordpress Blogs. Have to go through another battle w/ support on this. FUCK

Damn. That sucks foo.

Good luck getting it resolved.

yeah. was with hostgator for years w/ no problems and now 2nd time in 3 months w/ certified hosting. thinking about switching. shared hosting with a bunch of blogs but still having doubts on certified's security.

Let us know if you need help moving. :-)

mine looks good,
btw how to check if mine are infected ?

i m also on certified.

i logged into one of my sites and tried to log into the WP admin page. got prompted with a WP update page. Don't know if by clicking the update page if it triggered it or not. The links on the page were all to the domain and didn't appear questionable albeit the updates are always usually witihin the dashboard.

My main issue is that my sites are down until the base 64 encoding gets cleaned. Shouldn't the host have security stuff to stop that from in the first place? Twice in the past few months on my end. Like certified but the latest problems are troubling to me.

Might've been my bad, but overall the problem is insecurity IMHO.

that sucks man, happened to me with some host as well

Cyberwurx is doing great for me.

been keeping your wp updated?

wordpress.org can help too. always good to report the hack there as well, but sometimes not very helpful.

How do you know its their fault?

First negative post I've seen about them. Hope it works out for ya.

:2 cents:

it's not their fault...

your computer is infected...
I know since I've been there already..

you need to install Nod32 + Malwarebytes Anti-Malware and scan it. I guess you're still on XP so moving to Windows 7 would also help.

After that
if you use Filezilla - move to Filezilla portable
if you use Total Commander - download latest version and use master pasword for FTP
also use something for storing passwords in browser like RoboFrom, Keepass or similar...

my main issue was that w/ my prior host(s) never had WP problems with malware injections.

use a mac homer, sorry.... a ittle more techie that to still be using win xp. thanks though....

they are scanning and will let me know. props to their support since they are on the ball... my main concerns were with the ability for these sites to inject malware and all.

maybe overly concerned, maybe not.

Have you tightened up the default wordpress settings?

This is a MINIMAL security set :

• good and secure passwords
• rename the admin user
• change the table prefix from wp_ to something like wp2632361_
• check security permissions on main directories, check user groups
• update the WP as often as possible
• tighten upload security, if people can upload anything other than JPG, GIF
• add .htaccess to wp-content , wp-admin/uploads , possibly to specific plugins
• add .htaccess to wp-admin, double password check is pain in the ass, but if you are unsure about security it helps

Default WP installs are NOT secure, and running such blog is always a risk. There are tons of scripts out there that search for blog vulnerabilities and you don't have to be a genius to run one.

I doubt ANY hosting company will be checking default install of WP in shared environment for security holes. I'm not a Naked hosting customer, but my guess this is happening to you because of non-secure Wordpress setup, so it's not necessarily fault of the hosting.

Shared or dedicated?

I was going to ask the same thing. If it's shared it could be from another site infecting the server. Could also be a hijacker on your computer.

thanks all for the input. upon getting to the wp-admin page was getting a page with:

Database Update Required

WordPress has been updated! Before we send you on your way, we have to update your database to the newest version.

The update process may take a little while, so please be patient.

This is what started it i think. will see. they cleaned it up again. will see

shouldn't be possible on a properly set up server.