comment spam
Some idiot script kiddy wiped out our bandwidth again today. He could have an automated tool, or he could be doing it manually. He’s trying to post comment spam to blog.org, but he’s repeatedly fetching pages over and over again (presumably to see if his comments are getting published or not).
The problem is that David’s pages are large (and getting larger all the time); an average of 200Kb each. So this spammer has single-handedly downloaded at least 70Mb of data today!
It’s one thing to try to abuse my server to get a site ranked higher in Google. It’s another thing entirely to waste _my_ bandwidth in the process!
64.57.64.0/19, 66.154.0.0/18, and 66.154.64.0/19 just made it into the blackhole list…
4 Comments
RSS feed for comments on this post.
Sorry, the comment form is closed at this time.
I was kept busy removing the comment spam this created on the other end today as well (unfortunately, the script kiddies are starting to randomise their IP addresses and choose from long lists of URLs so IP address or URL blocking is less effective). Makes me think the only long-term solution to comment spam may be one of these type in the numbers from an image plug-ins. Though apparently determined spammers are actually doing it by hand! AARGH!
What about comment moderation in WP?
I’m using WP, and (as you can see) comment moderation is working.
David’s still using MovableType, and his weblog is quite popular…
I would recommend you setup some type of image number system so bots can’t spam!