I’m speaking at Wordcamp Albuquerque 2013 a week from today.  My session is called Hacked!  How they hack it and how you clean it where I’ll dissect a real-life WordPress hack and show everyone how I suavely and bravely root out the hacker, sleuthily determine how he got into the site, and then kick him out and slam the door behind him.

However, there’s a problem.  I figured there would certainly be a WordPress hack on one of our hosted customer sites between when I signed up for the talk a few months ago and now.  I’ve waited and waited, and shockingly, all of our customers have listened to us and have been keeping up with their WordPress updates.   So we haven’t had a single WordPress hack to clean up.

So I need this blog to get hacked.  The sooner the better.

Oh, and to speed this thing along and I’ve reverted this blog’s WordPress code back to WordPress 3.0.  This blog currently has more vulnerabilities than a president asking congress to approve a bombing on a mideast country.

I’ll update this blog and our twitter account with daily updates on my situation.  Stay tuned.   This could get interesting.  Or embarrassing.