Still Dealing With The Pharma Hack

I’ve been noticably absent lately, as I’m still dealing with the hacker issue I talked about a few weeks ago. While we were able to clean up the mess that they initially made, we hadn’t been able to get rid of them, and they’ve continued to wreak havoc with our sites. 🙁

Most people that deal with this issue have a single blog, and it’s easy to implement all of the hardening security protocols suggested. But when you have 50 sites, every little change has to be done 50 times. It’s been an absolute nightmare!

I’ve literally spent the past 3 days implementing drastic security measures, and hopefully they’ll give up and move on to the next unsecure site.

Chris Pearson has a post about the hack, and everyone’s been linking to it. Unfortunately, it doesn’t provide a lot of answers, namely how the hackers are getting access to the system. His situation is a bit different than ours, and I imagine that these guys are just adapting to the situations they face. It would be great if someone could pin-point the root cause, so we could all patch this up and move on with our lives.

Until then, fingers crossed.

Enjoyed this post?
Subscribe to Zander Chance via RSS Feed or E-mail and receive daily news updates!

Submit to Digg  Stumble This Story  Share on Twitter  Post on Facebook  Post on MySpace  Add to  Submit to Reddit  Fave on Technorati

2 Responses to “Still Dealing With The Pharma Hack”

  1. web design says:

    The blogging game is getting nasty with hackers coming into the scene and start fooling around.

    I been thinking would it be helpful if bloggers kept a set of their latest back up once changes was made to their blog. In the event the blog was hacked the system files can be restore to overwrite changes made by hackers.

    • Zander says:

      No doubt, regular backups are a must. And we had these in place – But unless the exploit itself was plugged up, there was nothing to stop the hackers from coming back and doing it all over again. (Which is exactly what happened!)

Leave a Reply