The Next Top Post

Filed under:Blogging — posted by Anwyn on July 12, 2009 @ 8:42 am

Another test. We’ve deleted what we think is reams of nasty code directly out of my database. If Daddyman really has cracked this problem, he might be able to document it for people like him who googled and found only that “yes, this problem exists, what’s happening here?” but no answers.

NASTY code, people. Reams of it. You better not be seeing any more of it on the feed to this post. Let me know …


  1. That one worked as expected, Anwyn. Think you got it.

    Comment by Allen — July 12, 2009 @ 9:14 am

  2. Not me–Larry dug it all up and chiseled it all out. (Knock wood.) It was incredible how much of it there was. :P

    Comment by Anwyn — July 12, 2009 @ 9:53 am

  3. Everything displays properly on Google Reader now, including the stuff that used to be spammy. One of these days you’ll have to post a technical explanation of what that code was, and how it ended up on your server (I assume it was there since Larry was able to delete it).

    Comment by Xrlq — July 12, 2009 @ 10:35 am

  4. The code was in the database, as I said in the post, and yes, on my server, where the DB lives. And yes, I plan to have Larry post an explanation. As I also said (more or less) in the post. ;) As to how, it’s impossible to say for certain “how” or “who”. Larry’s googling did turn up the fact that older WP installs have vulnerabilities that allow people to manipulate the php code and get into the DB tables. Nasty.

    Comment by Anwyn — July 12, 2009 @ 11:32 am

  5. D’oh. Reading Comprehension 101 for me…

    Comment by Xrlq — July 12, 2009 @ 3:03 pm

Copy link for RSS feed for comments on this post or for TrackBack URI

Leave a comment

Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>



image: detail of installation by Bronwyn Lace