Skip to main content

Please Don't Post Clickable Links to Malware Blogs

Every day, well intentioned bloggers post anxious demands in Google Blogger Help Group
This person listed their blog in several forums. As an admin of two of them, I have had many complaints over it about spamming. We have blocked his address from our forums, but it seems he has many of them and he keeps spamming it hourly.

Please shut this blog down.

So getting "" removed should be such a simple task, but it's not.

The problem is that, for everybody who reports a spam blog in BHG, someone else reports that their blog was just falsely accused of being a spam blog. Not every blog reported to be a splog actually is a splog, and not everybody reporting a splog actually is reporting a splog to get it removed.

So Blogger has to verify each spam blog report, before acting on a demand posted here.

Many spammers post in BHG
OMG, remove!

and while we wait for Blogger to take action, they watch their hits roll in, from a clickable link in their post. They know that, while we wait for Blogger to take action against the blog, their post will sit here, attracting the curious
I know that it's spam, but what sort of spam? I have nothing better to do, so I'll check it out.

By the time Blogger does anything, the spammer will publish
"", "", and so on. Next week, the spammer will post under another name
OMG, remove!

and watch the hits roll in for that one.

And the spammers will use millions of botted computers all over the world (maybe the payoff of the latest worm, such as Conficker / Downadup) and create thousands of splogs daily - "", "", "", and so on. Out of those thousands, one or two may get reported.

It would be real nice if Blogger would hire somebody to be more proactive and remove the spam blogs immediately. That same person could watch for the Indian Escort Service spammer in BHG, and axe the accounts used for each spam, immediately.

But, they won't.

So we have to take the initiative, and protect ourselves. Various security product providers (antimalware, firewall, and other security products) are providing browser add-on software, that will automatically scan each web page, and identify links to malicious web sites.

And, Google has provided a new form, for us to use to report the hacking, porn, and spam blogs. But making an entry in the form won't get the web sites removed, immediately - somebody will have to verify each accused blog. And a list of the verified guilty blogs will feed one of the malicious web sites databases. You may get some insight into the solution provided, in the Official Google Webmaster Central Blog: Better badware notifications for webmasters.

>> Top


Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: