Twitter Bombarded With WordPress Users Must Tweets

Reading time: 2 – 4 minutes

I have never expected that there’s going to be another trending topic on Twitter about WordPress attacks. Not at any point in time. It’s not something to cheer about because it’s a vulnerability that every self-hosted site running on WordPress must be alerted on particularly blogs.

I have once written a post about this vulnerability entitled, “Blogosphere Alert: Prevent your WordPress blogs from being hacked!” which takes into account the ordeal that I’ve gone through and how I faced it with much ardor.

Now that this is happening again (at least not on this blog), this took me back into the experience of how this blog was challenged and how I responded. Of course, no person would ever want something he has accomplished go to waste so I went all out in solving the issue myself.

“WordPress Users Must” is the trending topic on Twitter at the time of writing so I have decided to tweet my previous post about this issue for others to read because I know that it can certainly provide valuable information to many. In fact, I even took the time to comment on Lorelle’s blog regarding her post entitled, “Old WordPress Versions Under Attack” hoping that somehow I could contribute to the conversation.

What I find annoying is like most trending topics on Twitter, affiliate schemes tend to take advantage of it having tweets containing links pointing to affiliate landing pages and a bunch of unrelated tweets just mentioning the phrase. Take a look at the screen shot below to see what I’m talking about.

WordPress Users Must - Trending topic on Twitter during the WordPress Attacks on September 2009

While Twitter still don’t have any algorithm to filter out which tweets are relevant to the topic, then it’s your job to do it. My only advice is you follow the steps I’ve mentioned on my previous post about this blog being hacked and always be in the lookout.

Suggested for further reading:

1. Blogosphere Alert: Prevent your WordPress blogs from being hacked! Reading time: 6 – 10 minutes I was surprised...
2. Secure Your Blogs: Upgrade to WordPress 2.8.5 Reading time: 2 – 2 minutes Just recently, the...
3. PHP Script Vulnerabilities and WordPress Blog Hacking Reading time: 3 – 4 minutes Based on my...
4. Cleaning Up the Twitter Clutter Reading time: 2 – 2 minutes I have been...
5. StalkDaily.com Worm infects Twitter overnight Reading time: 2 – 2 minutes Last Saturday, Twitter...

Did you enjoy this article? Please subscribe to Software Critics via RSS or Email to receive all the FREE updates!

Tagged as: avoid blog hack, blog threat, hack, Login LockDown, open source, prevent blog hacking, stop blog hacking, website threat, WordPress, WordPress attack, WordPress hack, WordPress security attack, WordPress security threat, Wordpress vulnerability

4 comments