There is one problem with hosting a blog on your own webspace: No matter how hard you try to keep everything secure, every once in a while someone breaks through your defenses and hacks you. Unfortunately, that happened to me sometime late Sunday night or early Monday morning.
Everything was OK when I went to bed on Sunday, but Monday morning when I tried to log in and approve the droves (ha!) of comments in my queue, I got a message that my website was an “attack site.”
Although I had plenty of other things to do, I spent all day Monday going through the plethora of files on my website hunting malicious code. It was not a fun way to spend my day off.
There was one benefit to the attack though: I have had my domain name for seven years and have had a website in one form or another for about twleve. While I have periodically deleted files that were no longer serving any purpose, I hadn’t done so for at least two years. Many of these files were ones that had been hacked, so by examining each file for malicious code I was also able to determine which pages were doing little more than sitting out there begging to be attacked.
Since my website is now (more or less) synonymous with my blog I removed all the static pages (some of those pages may return at a later date in a different form), removed the malicious code from the ones that were staying online, reset my passwords, and resubmitted my site to Google to verify that I had fixed the problem and get back in their good graces.
I apologize to anyone who may have tried to access my site during this time and highly encourage you to run a spyware and/or virus scan to make sure that those hackers weren’t able to install anything on your machine.
My website is clean again so please come back to visit me. I promise you that I will be doing everything I can so an attack like this doesn’t happen again.