I’ve always known that the Internet was a bit like the Wild West, that if you turned the wrong corner there’s be the aggressive stall holder tugging at your sleeve to sell you some over-priced piece of knock-off junk while simultaneously picking your pockets while his dodgy looking mates beckon you towards a manky shed where you can hear the faked pants of the live sex show taking place on a filthy mattress inside. I’m not naive about the lawless side of things – I did some fairly comprehensive research that side of things when I was researching Devil, my first book, and I’m well aware of how out of date that research is now. But even so I didn’t see it coming. I thought this blog was a pretty safe place to hang out, a little bastion where I could whether the storm quite happily for as long as I wanted to.
Now that was naive.
It happened on my wedding anniversary. I only noticed that once I had saw the damage a few days later. They hadn’t known of course – but that coincidence made it feel like an utterly personal attack, a violation. My blog, this site, which I’ve been building since 2008 despite the fact I haven’t been posting as often as I should for quite a while now, had been hacked. It was a particularly nasty kind of hack known as the Pharma hack – or at least a variation of that hack. It works by highjacking your site as it appears in Google search results so that your site advertises whatever they happen to be selling – as the name suggests it’s often pharmaceuticals, in my case it was games. It’s a particularly annoying hack because it’s hard to detect. It only shows up in Google searches, everything looks fine on Yahoo or Bing and if you go directly to the site it’s absolutely fine. It usually effects the most popular links to your site – so in a way it’s the most backhanded of backhanded compliments. You only get affected if you’re doing something right.
So I was stuck with a website that, as far as anyone looking on Google was concerned, did a very good line in Fifa games in Polish. I changed every password I could think of and got onto my hosting company to ask for assistance but was told it was down to me to clean up. One of the staff might be willing to do it as a nixer – for a price. So I started doing my own research. It seemed the hack was quite common. It also seemed that getting rid of the hackers was not the easiest thing in the world. But there was good advice out there – in particular this WordPress forum and this excellent post. I started looking for the code the hackers had added to my site – but while I managed to find the files modified on the day I knew they got in, I couldn’t find the (hidden) code.
So I decided to take drastic action. If the hackers were going to squat on seven years of hard work because I’d managed to get some kind of Google Rank then I’d make sure it wasn’t worth their while. I’d whip the rug from under them. I’d burn the place down.
Ok there were probably better ways of doing it. Ways that wouldn’t have trashed my own ranking, especially since Google seemed blissfully unaware that I hadn’t just switched my line of work. But I’d had enough. Like I said, it felt personal. I suppose that’s what I get for having a self-named website – it’s all going to be ego in the end.
So I blew the whole thing up. I deleted the database and uninstalled the WordPress installation. Then I started deleting everything else I could find – except a load of folders that I didn’t have access to – where the backdoor actually was. It was actually rather liberating – in a decidedly destructive way. I’d backed up all my posts from WordPress (and thought I had all the images and sound files I’d uploaded over the years). What could possibly go wrong? At this stage my faith in the Internet was somewhat restored when Good Samaritan came forward on Twitter and offered to give me a temporary place to call home – without which I seriously doubt I’d have got things restored to the stage they are at the moment.
It took a while to sort out but I changed hosts and transferred my domain to the new guys. I wasn’t happy with the way my old hosts had dealt with things. OK I had been naive about the level of security needed but there should have been a bit more by way of support there. I had always felt with them that there was an attitude that if I didn’t know how to do something I shouldn’t really be managing my own website. I might not be madly techy but I’m independent. If you bother to explain how something works, or at least point me in the direction where I can learn more, I will read up. I’m learning as I go – and the past six weeks has been a very steep learning curve.
So for the past week I’ve been putting everything back in it’s place, here in it’s new home. I’m far happier with the new hosts – they’ve been absolutely brilliant as I’ve been getting set up, no matter how trivial the question. The damage has been done with Google but I’ve been working on the SEO. It doesn’t help that I’ve sort of changed address – there’s now a /wordpress/ missing in every link – so I’ve been setting up redirects left right and centre and doing a bit of firefighting. Hopefully everything will settle down eventually. What all this has done is meant that I’ve had to go back over all my old posts. It’s made me remember why I started this blog and why I kept it going. Over the past few years I’ve let things slide. Well from now on I can’t promise that I’ll post as much as I did when I had a book to sell but I’ll make more of an effort. I’ve already been tweaking the look of the thing – this will be an ongoing process – I have a very clear idea of what I want – but I’ll need to learn a bit of CSS first.
And if I do things right and make another tempting proposition for the hackers I’ll be ready for them next time. I’m not going to get caught out like that twice – next time I’ll go all Charles Bronson on them!