We Were Hacked…

This past weekend (and again today), CWDG and every other blog I run was hacked. I’m still sorting all of this out and it’s an absolute nightmare. Seriously, I was *this* close to just closing down everything. My feelings haven’t changed all that much since then.

For now, it seems to be okay, but I’m still looking for the backdoor (how the hacker accessed my site). I’ve done the basics like totally reinstalling wordpress, installing anti-virus on the blogs, adding a tighter security plugin, etc. I’ve scanned my own computer (which runs on Linux) for viruses (it’s clean), and have scanned CWDG with five or six online scanning services (all of which show it as clean). I also subscribed to the (probably BS) security scanner offered by my hosting service for $5 a month. Also, anyone that had a login account on CWDG – you now do not. Just covering bases here, and I apologize for the problems.

For those who want to know, the hacker placed a base 64 decode script in my themes’ index.php files. This would normally go undetected, but apparently the CWDG’s theme index page is so poorly written that the virus broke it and alerted me that something was up.

Again, I think I might have fixed it for now. I also have to fix the two other blogs that I run. Technologically, I’m in way over my head, so I don’t really know what I’m doing here.

Worst of all, I had to skip a day of writing to do this. Needless to say, I am really REALLY not happy.

Thank you to the several people who emailed me about this. It was a really big help. I appreciate it.


View all posts by

9 thoughts on “We Were Hacked…

  1. What a horrible thing to do! Please don’t lose heart – your site is an absolute gem and it would be a tragedy to lose it.

  2. Don’t give up! You’ve put far too much work into this. It’s an awesome site! Besides, I need my daily dose! You can’t leave us hanging; how will we ever find out how the war ended?!

  3. Damn shame. Sorry somebody felt the need to screw with your sites. I can’t imagine why a Civil War Site, a travel log, and a record/music review site would be worth attacking. Keep your chin up. A lot of us look forward to what you do.

  4. For whatever it’s worth, when I tried to access the website from work at lunch, the company firewall detected something and threw up a warning page. (I work at Boeing, which as you might imagine is a major industrial espionage target.) There must be way to detect the script besides breaking the index page.

  5. Sorry this happened to you. My Norton blocked something called “toolkit” Sunday and Monday and I noticed that the site did not present the postings. I chicked on the left side photo for the day to access the posting each day. So I figured something was happening, but did not know what. I am not a tech person. I just operate. For the record, I have not had any problems after accessing the daily postings, but I do have Norton which is one of the best in my opinion.

    Thank you for your faithfulness to us fans. 🙂

  6. Thanks, everybody!

    More than likely, it wasn’t a personal attack. My host may have been targeted (hosts often are), but it wasn’t some disgruntled yankee/reb thinking that I’m too far right or left in my interpretation of events.

    Hopefully, the drama is behind us.

    Kevin, what do you mean? The comments are still here, right?

Comments are closed.