Comments on: Spam Link Injection Hacked (and How I Hopefully Fixed It)

By: dibo

dibo — Wed, 12 Aug 2009 16:26:18 +0000

Exact same thing happened to me. Same links too. I think it was an exploit in the WordPress code so a malformed SQL query inserted all the links but I did all the things you did just to be safe.

By: Evil Mammoth

Evil Mammoth — Wed, 05 Aug 2009 18:22:52 +0000

That’s great. I’m hoping I have the same success when I implement your changes.

I had already done a few of them a few days ago with no luck, and I’m getting real tired of these assholes.

Keep up the good work. I’ll be checking in. Glad I stumbled across your site.

By: Chris Coyier

Chris Coyier — Wed, 05 Aug 2009 18:20:03 +0000

Still clean as of this date! Thank god.

By: Evil Mammoth

Evil Mammoth — Wed, 05 Aug 2009 18:16:24 +0000

I’ve had a similar thing happen. I was just wondering, as of a month later, what the status is. Have you had further troubles with the spammer?

Thanks again for this guide and writing this post.

By: Aaron Moodie • Kill All Spam

Aaron Moodie • Kill All Spam — Mon, 03 Aug 2009 08:18:48 +0000

[...] it doesn’t happen again. If anyone else runs into this trouble, there are some good posts here and here on how to best remove the links, and Smashing Magazine has a great article on beefing up [...]

By: Matt Gibson

Matt Gibson — Sun, 05 Jul 2009 20:17:22 +0000

Scary. One thought springs to mind; I wonder how easy it would be to create a Yahoo pipe that took an RSS feed and made a feed of the raw source? At least if you were subscribed to that for your own sites you’d see the problem fairly quickly…

By: BlogBuzz July 4, 2009

BlogBuzz July 4, 2009 — Sat, 04 Jul 2009 10:17:33 +0000

[...] Spam Link Injection Hacked (and How I Hopefully Fixed It) [...]

By: Joel Oliveira

Joel Oliveira — Wed, 01 Jul 2009 22:57:26 +0000

It hasn’t been mentioned here yet and I think it deserves inclusion – http://blogsecurity.net/wpscan

The security scan there is helpful, not to mention the entirety of the blogsecurity website. I’ve used it a couple of times on a few sites and it’s caught a few things that helped me lock things down. First thing I do these days w/wordpress – remove that admin account. I think that’s the root of a good number of vulnerabilities.

By: Len

Len — Wed, 01 Jul 2009 05:44:21 +0000

You said that you changed permissions of wp-config.php to 755. Rule of thumb,

files – 644
folders – 755

By: redwall_hp

redwall_hp — Wed, 01 Jul 2009 00:10:27 +0000

Contact Google, whether through Matt Cutts or a more official method, and explain what happened to them. They have the power to fix it, and very well might help you out.