Social Icons

Pages

Showing posts with label Spam Review. Show all posts
Showing posts with label Spam Review. Show all posts

Saturday, 14 December 2013

Blogger Blog Content Needs To Be Unique, And Properly Targeted

I've been studying spam, in Blogger blogs, for over 5 years.

This year, we've seen improvement in the automated spam classification process, implied by a noticeable reduction in spam review requests overall - and in a considerable reduction in the proportions of false positive classifications. During the past few months, blogs requested for review are 2 or 3 times more likely to be confirmed as legitimate spam blogs (true positives), compared to this time last year.

Of the blogs confirmed to be spam hosts, when I am able to examine cached copies of the content, 3 out of 4 of those appear to contain material scraped or syndicated from other blogs or websites.
  • Content scraped (stolen), or syndicated (copied, with permission), from other blogs / websites. Content scraped or syndicated to other blogs / websites.

Google describes the problem, in Blogger Help: Spam, phishing, or malware on Blogger, quite simply.
Spam blogs cause various problems, beyond simply wasting a few seconds of your time when you happen to come across one. They can clog up search engines, making it difficult to find real content on the subjects that interest you. They may scrape content from other sites on the web, using other people's writing to make it look as though they have useful information of their own. And if an automated system is creating spam posts at an extremely high rate, it can impact the speed and quality of the service for other, legitimate users.

Long ago, spam blogs were first encountered as startup components in large spam blog farms.

Later, we explored the involvement of various "get rich quick" schemes, and of affiliate marketing.
  • Content or links which reference referral-based activities such as GPT ("Get Paid To"), MLM ("Multi-Level Marketing"), MMF ("Make Money Fast"), MMH ("Make Money from Home"), PTC ("Pay To Click"), or PTS ("Pay To Surf").
  • Affiliate marketing (Please, don't confuse this with "affiliate networking"!).

Of these three broad descriptions of confirmed spam blog content - spam blog startups, get rich quick schemes, and affiliate marketing - the one common feature in most of the blogs, confirmed as spam hosts, seems to be the lack of unique content. One of the features of the Panda update to Google Search was described as "content quality" in search results.

The past year tuning to Blogger spam classification appears to be in keeping with Panda, in that it is targeting blogs which rely upon content intentionally replicated from blog to blog - whether "scraped" (stolen, without permission), or "syndicated" (copied, with permission).

The end result here is that Blogger blogs, to avoid spurious spam classification, need to contain as much unique material as possible. While some amounts of quotation of other blogs and websites is beneficial, the majority of blog content needs to be written by the blog owners and contributors, and properly targeted to the reader population.

>> Top

Sunday, 18 August 2013

CAPTCHA Verification Is Broken, For Some Blogs, In Various Applications

We're seeing a number of problem reports, in Blogger Help Forum: Something Is Broken, about various problems which involve CAPTCHA verification processes.

The symptoms are fairly diverse.
  • Some blog owners report problems with commenting, on their blogs.
  • Some report problems with high posting volumes.
  • Some report problems getting abuse review requested, for their blogs falsely accused of hosting abusive content.
The reporting volumes, and perceived urgency, for each case, will vary.

The known problems involve various bX codes, issued in place of the CAPTCHA form.
  • An unverified code is being seen, by people trying to post comments, on blogs using CAPTCHA screening.
  • Blog owners are reporting various bX codes, when trying to post high volume blogs.
  • Other blog owners are reporting "bX-niui1k", when trying to request spam review, from the dashboard "Deleted blogs" list.
  • It's possible that there are other CAPTCHA applications, also seeing bX codes.
The audience observing the bX codes will differ - because the relationship of the people needing to use the CAPTCHA, and the volume of CAPTCHA use by the affected people, will differ.

People observing a bX code, when trying to post a comment, will be guests on blogs which use CAPTCHA screening - since blog members and owners are not subject to comment screening. CAPTCHA screening is optional for comment moderation, in general - and it's possible that many blog owners are not using CAPTCHA screening on their blogs.

It's also possible that only blogs which use the full page and popup comment forms are vulnerable, to this problem. The report volumes involving bX codes involved with comment moderation are low - and this will make affinity analysis difficult.

People observing a bX code, when trying to post at high volume, will be blog owners who post frequently. The reports of this problem are low to medium volume - possibly because many blog owners avoid posting excessively. This may be because we have observed that repeatedly solving a CAPTCHA will be inconvenient.

The people who report this problem are fairly insistent that this problem needs to be solved. Since the bX code is observed repeatedly (once for each high volume post attempted), by the blog owners affected, this case will involve the most controversy. Several blog owners have reported seeing differing bX codes.

People observing a bX code, when trying to submit an abusive blog review request from the "Deleted blogs" dashboard list, will be blog owners whose blogs were deleted or locked, spuriously, for abusive content (aka "spam hosting"). These people will post in the forums, and can be helped fairly easily, by our promptly offering a manual review, submitted to Blogger Support.

This case represents the most frequently reported symptom - but since the people affected can be helped with minimum fuss - and since this case is only observed once for each blog involved, this case will involve less controversy. This case has been reported, as noted, consistently producing the "bX-niui1k" code.

It's possible that CAPTCHAs are used in other unidentified applications - and we may yet have other cases to discuss, if the base problem is not resolved fairly promptly. Blogger Support is currently aware that there is a problem - and hopefully, where the problem lies.

>> Top

Thursday, 27 June 2013

"Adult Content" Blogs, And New Blogger Monetisation Restrictions

This week, we're seeing some reports from a few blog owners who recently received a disturbing email message, mentioning their blogs and adult advertisements.
I received an email stating I have adult content on my blog, and that a new policy will cause certain blogs to be deleted. Is my blog vulnerable to deletion, under this new policy?

Like many spammers, these blog owners may be asking for a whitelisting of their blog - which is something that Blogger just won't provide.

The legendary email, recently received, is somewhat ambiguous in wording.
You are receiving this message because you are the admin of a blog hosted on Blogger which is identified to have Adult content.

Please be advised that on June 30th 2013, we will be updating our Content Policy to strictly prohibit the monetization of Adult content on Blogger. After June 30th 2013, we will be enforcing this policy and will remove blogs which are adult in nature and are displaying advertisements to adult websites.

If your adult blog currently has advertisements which are adult in nature, you should remove them as soon as possible as to avoid any potential Terms of Service violation and/or content removals.

The policy discouraging monetised "adult content" blogs is not new - we have actually been warning people about this for years, in the Malware / Spam Appeal Guidelines. We cite the Guidelines a dozen or so times daily, in various malware and spam review discussions in Blogger Help Forum: Something Is Broken.
Blogger / Google has repeatedly stated that some blog content is not acceptable, because it constitutes or encourages abusive activity, such as hacking, porn, and spam, in the Blogger Internet space.

Here is the current list of examples, developed by Blogger / Google, and the Top Contributors of Blogger Help Forum.
  • Affiliate marketing (Please, don't confuse this with "affiliate networking"!).
  • Automated traffic redirection, to another Blogger blog, or to non Google hosted content.
  • Commercially funded adult content.
  • Content created with scripts and programs, rather than by hand.
  • Content or links which reference account hacking / password distribution / password sharing.
  • Content or links which reference code deconstruction / reverse engineering, to bypass normal use of proprietary
  • software.
  • Content or links which reference referral-based activities such as GPT ("Get Paid To"), MLM ("Multi-Level Marketing"), MMF ("Make Money Fast"), MMH ("Make Money from Home"), PTC ("Pay To Click"), or PTS ("Pay To Surf").
  • Content scraped from other blogs / websites.
  • Copyright Infringement.
  • Large blogs with multiple, unfocused / unrelated subjects.
  • Links to Illegal Downloads / Streaming / Torrents.
  • Monetizing of adult content, aka porn spam.

The specific blogs, targeted by the email, are not difficult to identify. "Adult Content" blogs will generally bear an interstitial "Content Warning", awarded either voluntarily or involuntarily.

In odd cases, people may receive the email, but may not have any blogs affected by the policy - and in this case, they will simply have to ignore the email. Blogger Support can only review blogs, when they are actually deleted or locked.

In other cases, people may not receive the email. Just as with malware and spam classifications, all blog owners won't be contactable by email.

If the adult content classifier is designed similar to the malware and spam classifiers, it will use a fuzzy detection process to identify the undesirable "adult content" advertisements.

Since fuzzy malware / spam classification does not support whitelisting, porn classification won't either. Blog owners asking "Is my blog safe?" are unlikely to get any useful answers.

My suspicion is that owners of the most popular and productive "adult content" blogs will move to alternate hosting. Some of them may relocate to WordPress - until WordPress, similarly, rejects them.

Some owners, choosing to remain in Blogger, will take the warning seriously, and remove any ads.
If your adult blog currently has advertisements which are adult in nature, you should remove them as soon as possible as to avoid any potential Terms of Service violation and/or content removals.
Various possible "adult content" blogs, with and without "adult advertisements", remaining in Blogger hosting, will be classified and deleted, and will result in more reports in Blogger Help Forum: Something Is Broken.
Why was my blog deleted?

We'll simply end up with more discussions with requests for review and reinstatement - and more uncertainty. Some blogs will be restored promptly, with others requiring careful deliberation. And some blog owners will simply be told
Sorry, your blog cannot be restored. It was recently confirmed as a adult content host, with unacceptable advertisements.


>> Top

Sunday, 10 March 2013

Blog Owners, Unable To Request Restore Of A Deleted Blog

One of the more intriguing issues, seen in Blogger Help Forum: Something Is Broken, involves people unable to recover control of their blogs.
I recently changed ISPs, and now I can't login to update my blog.

Occasionally, this issue becomes more complicated, because the blog is deleted - and the owner can't request that it be restored, using the automated review request wizard. Sometimes, the would be blog owner may to try to bypass the current blog recovery policy, by claiming special circumstances.
The blog has been deleted. I received no suspicious activity or password change notification emails, or emails of any kind related to my blog.

What is the story here? Can blogs just disappear from the Blogosphere, without the involvement of the blog owners - and be unrecoverable?

Recovery of a deleted blog starts with the requirement that only a blog owner can un delete a deleted blog - and this is where many mysterious disappearances start.

Since a Blogger blog is the property of the owner, and the owner is allowed to delete a blog any time required, it would not be right to let people who are not the owner un delete a blog - or demand that the blog be un deleted. To enforce this requirement, Blogger added the dashboard based Restore wizard.

Since only the owner will have the deleted blog listed in their dashboard "Deleted Blogs" list, only the owner can request restore of the blog in question.

The dashboard Restore wizard serves blog owners, with blogs deleted under various circumstances.
  • Deleted by the owner.
  • Deleted by Blogger, as a suspected spam host.
  • Deleted by Google, for TOS Violation.
Any deleted blog will appear in a special dashboard list, "Deleted Blogs" or "Locked Blogs" - when it can be recovered. If the blog is not recoverable by the owner, there may not be a link.

There are specific cases where a deleted blog may not be recoverable using the recovery wizard.
  • The blog is locked, pending integrity check (following account lock for suspicious activity).
  • The blog is owned under a different Blogger account, and is listed on another dashboard, under "Deleted blogs".
  • A blog owner deleted the blog, long ago - and the blog is no longer recoverable.

A blog locked, pending integrity check, cannot be requested for restore. The owner has to first have the owning account unlocked. Similar to the account recovery process, Blogger / Google will require that the owner provide proof of ownership, before the account will be unlocked. With the account unlocked, security specialists will inspect each blog owned by the account, and verify that each does not contain evidence of tampering by a temporarily successful hacker.

While a blog is under integrity check, it won't be listed on the dashboard of the owner - either under "Deleted blogs", "Locked blogs", or "My blogs". Neither the owner, nor any third parties, will be able to do anything except wait, patiently.

Blogs found to contain malware can be locked as TOS Violations, with the owner later required to remove the malware found. This requirement will apply for malware installed by the owner (intentionally, or unintentionally), or for malware installed by a hacker.

With a blog locked pending malware removal, the owner is given the benefit of the doubt, and allowed to simply remove the malware, no questions asked. In some cases, Blogger may be able to assist by providing specific identification of the malware found - but this won't happen, consistently.

A blog owned under another account must be un deleted by the owner of the other account. Again, only a blog owner can have a blog restored - whether deleted by an owner, or by Blogger / Google.

A blog deleted over 90 days previously cannot be recovered. It won't appear on the dashboard of any (former) owner, since it can't be recovered.
It's dead, Jim.

The basic rule is simple. If your blog was deleted, and if you're able to un delete it (or request un deletion), you'll have a link on your dashboard. If a blog is not listed on your dashboard, you can't request, with any predictable success, that it be un deleted - any more than you can demand that a non deleted blog be restored to your control.

>> Top

Tuesday, 5 February 2013

A Blog Deleted, As A Suspected Spam Host, Is Not Subject To The 90 Day Limit For Restore

We see signs of panic, periodically, in Blogger Help Forum: Something Is Broken, about blogs deleted as suspected spam hosts.
My blog was deleted for spam 2 months ago. I need my blog restored, this month, as I don't want to lose it!
This is a common misconception, about spam deletions, and the mysterious 90 day limit.

There's no deadline for either the start, or the completion, of the review process, when a blog is classified as a suspected spam host. The owner may request review a year after the blog is deleted - if he's willing to wait for a year without concern. Alternately, he may ask for review the same day that he discovers the blog is offline. When the review is requested, Blogger Support may be immediately available, and may return a blog to service that same day - or they may be busy, and require a month to respond.

When the blog does get reviewed, the rules are simple.
  • If the blog is judged to be righteously classified, the blog is deleted, with the URL locked to the deleted blog.
  • If the blog is judged to be spuriously classified, the blog is restored, and control is returned to the owner.
In either case, the URL is not made available to the public.

This is either good news (if you are the owner), or bad news (if you wish that you were the owner).

You cannot gain control of the blog, or of the URL, by reporting the blog as a spam host - whether the blog has 1 post (one post published 10 years ago), or 3650 posts (one post published daily, for 10 years). If the blog appears to be inactive, your only option is to contact the owner, directly. If Blogger classifies an inactive blog, following your reporting the blog as a spam host, the blog will remain deleted or locked, until the owner requests review.

If the owner deletes the blog, the URL may - or may not - be made available.

Pick an available URL, and start your blog - and concentrate on the interests of your readers.

>> Top

Saturday, 19 January 2013

Blogger Cannot Provide Advance Warning Of Malware / Spam Hosting Deletions

One of the more intriguing tales, in the never ending saga of malware and spam interdiction, would have to be the confusion about the proper procedure for deleting or locking blogs, when suspected of hosting malware or spam. We periodically see, as part of a "Please unlock my blog!" request in Blogger Help Forum: Something Is Broken, the naive suggestion.
It would be better if Blogger Support had immediately alerted me of this problem, before deleting my blog!
The irony here is that, from a purely "customer service" viewpoint, I have to concur with the principle here.

It would be better, if Blogger Support could do this. Like many "it would be better" observations, this is probably never going to happen.

What would happen, if Blogger were to provide advance notification of any malware / spam classification? Many spammers would certainly appreciate this option - to remove the dodgy content, before the blog is deleted or locked. The typical spammer would have several options.
  1. Remove the dodgy content, immediately.
  2. Copy the entire blog to a second blog in the spam blog farm, and wait until receiving advance notification for that blog. Lather, rinse, repeat.
  3. Possibly, do nothing. Later, claim indignantly
    I never got the notification!
    and hope that the kind souls at Blogger Support would give him another chance, since he had not been properly warned.

Option #1, used wisely, could even be used to "map" out the current spam mitigation strategy, and let spammers publish hundreds of spam blogs, staying below the radar. Essentially, we would see self whitelisting of spammy blogs. What spammer would not go for that, in a second?

Besides the spammers benefiting hugely from advance notification, not all genuine blog owners would benefit. Not every blog owner uses a properly registered Blogger account, or will read email from Blogger Support.

So, we have two downsides to the option of advance notice.
  • Spammers would love it.
  • Not every non spammer would appreciate it.
I, for one, don't see an upside - or certainly not any upside with benefit to counter the downsides.

In Utopia, there would be no spammers, and no need for any of this. Unfortunately, the Internet will never be part of Utopia.

>> Top

Friday, 11 January 2013

Benefits Of The New Dashboard Based Spam Review Request Option

The improved spam review option has been available, on our dashboards, for slightly less than 2 months. For all it's usefulness, it appears that some blog owners see the new option as just another bit of red tape, which prevents them from publishing their blog. We see suggestions in Blogger Help Forum: Something Is Broken, periodically.
Can't you just submit my review request now, without making me wait another 2 days? Is my dashboard review request really necessary?

Unfortunately, the better the dashboard based spam review option works, the more this confusion should be expected.

Long ago, we had a "Deleted Blogs" link on the previous Blogger dashboard. That link, and the hidden list, were obscure - and explaining how to find the "Deleted Blogs" list was not a job for the weak or impatient. When a blog owner would post in the forums
Why was my blog deleted? I am not a spammer!!
we would typically reply, immediately, with the notorious Spam Appeal Guidelines - then later, cooperative blog owners would see
Your appeal is forwarded to Blogger Support ...

In order to speed up recovery of the less spammy blogs - and shorten the restore wait time for all deleted blogs, Blogger Engineering added the dashboard based "Restore" button. The new button serves two functions.
  1. For blogs deleted by Blogger, that are marginally spammy, the blog owner can request an expedited review.
  2. For blogs deleted by the owner, less than 90 days previously, the owner can easily restore his own blogs, as convenient.

The new button serves several groups of people, in various ways.
  1. Owners of less spammy blogs benefit by expedited restore. When successful, they see their blogs possibly restored on that same day, without their spending any time in the forums.
  2. Owners of marginally spammy blogs benefit by regular review and restore, from a shortened queue - since some blog owners will use the expedited queue.
  3. Blogger Support can spend less time with the marginally spammy queue, and produce quicker turnaround - yet spend more time examining the truly spammy blogs.
  4. Only the genuine spammers will not benefit from the new review queue.
This produces a Win - Win - Win - Loss (sorry, Spammie) scenario.

The blog owners who get their blogs back in a few hours probably won't post in the forums, and praise the improvement - they will be busy re publishing their newly recovered blogs. We may see more oblivious spammers, because Blogger Support will able to spend more time examining truly spammy blogs - which should encourage Blogger Engineering to tweak the automated spam classifier, into digging deeper into the Blogger Blogosphere. So we should expect to see more posts in the forums, for a while.
Why was my blog deleted? I am not a spammer!!

And, it's possible that not all deleted blogs will be listed by the "Deleted Blogs" wizard.

>> Top

Wednesday, 5 December 2012

Adding AdBrite Ads To Your Blog May Cause Spurious Spam Classification

For several months, we've been seeing reports from various Blogger blog owners, about yet another possible source of spurious spam classification.
I just received the email:
Hello,

Your blog at http://yourblog.blogspot.com/ has been reviewed and confirmed as in violation of our Terms of Service for: MALICIOUS_JAVASCRIPT. In accordance to these terms, we've removed the blog and the URL is no longer accessible. For more information, please review the following resources:

Blogger Terms of Service: http://blogger.com/terms.g
Blogger Content Policy: http://blogger.com/go/contentpolicy

-The Blogger Team

This happened almost immediately after I added HTML script recommended to me from AdBrite.

Use of the dashboard review request will generally repeat the originally offered verdict.
MALICIOUS_JAVASCRIPT.
In most cases, final review, when properly requested in the forum, will finally result in the blog being restored.

Review of various discussions in Webmaster Central indicate that AdBrite is not well regarded, in anti malware circles. One helper there suggested that AdBrite has a problem with security, allowing spammers to publish into their service - which puts unacceptable content on the blogs showing their ads.

If you want to publish a Blogger blog which does not get periodically locked as a suspected spam host, you might want to consider using a different ad hosting service - and to remove any similar third party gadgets from your blog.

>> Top

Saturday, 1 December 2012

The Dashboard Spam Review / Undelete Option Can Be Used To Your Advantage

Recently, Blogger added an improvement in the spam review process, to help shorten the review cycle. Blogs that are deleted or locked, as suspected spam hosts, are now listed on the dashboard, behind a "Deleted blogs" / "Locked blogs" button or link. Each blog, deleted or locked by Blogger, can be submitted for an automated review, by using the "Restore" button next to any blog listed.

Not all blog owners see the benefit of the new option. Some owners think this represents yet one more hurdle, in the endless protocol.
I just want my blog restored! Can you please just forward my review request, without the red tape?

Many blog owners don't realize the benefits of the dashboard based spam review request wizard.
  • Many blogs, with review requested by the dashboard link, can be reviewed, and restored, within 24 to 48 hours.
  • Blogs restored after dashboard based review request don't require the owner to spend time in the forum, requesting review.
  • Blogs restored after dashboard review request don't require Blogger Support to spend time conducting a manual review.
Use of the expedited, dashboard based review process shortens the review process for everybody.

There's a special benefit during weekends. Blogs submitted for manual review will sit in the review queue for at least 48 hours, when no Blogger staff are available to conduct the review. And that 48 hours starts only after the review request is forwarded to the Blogger Support review queue.

Many forum based review requests are recognised, by the helpers, hours - or days - after the forum topic is posted by the blog owner. The forum based latency causes frustration for everybody, and further delays the forwarding of the request. And some review requests can be processed only when key Blogger Support personnel are available.

Use of the dashboard based spam review request makes it easier for everybody. And this helps the forums run smoother - and more blog owners and readers can be helped.

>> Top

Tuesday, 20 November 2012

Improved Spam Review / Undelete Option In Blogger

One of the more positive changes in the "New GUI" involves an improved ability to find, and correct, deleted and locked blogs.

Finding deleted / locked blogs, under earlier versions of Blogger, was always a challenge - both for the person looking for the necessary display - and for the people trying to instruct how to find the necessary dashboard display.

In the current Blogger dashboard, one simply logs in and looks for the "Deleted Blogs" button - right beneath "New Blog", when the blog owner has any self deleted blogs, or any blogs deleted or locked by the Blogger abusive blogs classifier. Clicking on "Deleted Blogs", we see a list of blogs - with either an "Un delete" button (for self deleted blogs), or a "Restore" button (for spam classifier locked / deleted blogs).

Neither the "Restore" or "Undelete" button produce an immediate or universal result - both are still subject to previous limitations.

It is simply now far easier to find the spam review / un delete mechanism, than it was under the previous GUI.

If your blog was deleted by you - or deleted by Blogger for hosting malware, you should be able to hit "Restore", and the blog will be restored while you wait. If the blog was deleted or locked by Blogger for suspected spam hosting, you will probably have to solve a CAPTCHA - then wait 24 to 48 hours, while the blog is reviewed. In the long run, you will probably find this extra effort will be worth your time.

In some cases, the owning Blogger account may be locked, following unusual account activity - generally, brute force password guessing attempts, in an effort to hijack control of the account and any owned blogs. After submitting an account restore request and / or changing the account password, the blogs owned by the account will be restored - generally 24 to 48 hours after the account is restored. This is a normal, and unavoidable, result of Google, protecting your account and blogs from hacking activity.

Just be aware that not all blogs will be listed by the "Deleted Blogs" wizard.

Please be aware of the limitations of the restore process. This process serves blog owners who have been spuriously classified. If you request restore - and Blogger confirms that you are a spammer - you will be best advised to start over, or to find a different platform for publishing.

If you do start over, you should be very careful, and avoid making the same mistakes - lest you be subject to more strict punishment. Spammers simply are not welcome, in Blogger / Google - sorry.

>> Top

Wednesday, 12 September 2012

How Not To Make Your Blog Private

Blog owners have been asking, for years, how to protect their blogs against viewing by undesired or unknown readers.
How do I password protect my blog?
When told that Blogger password protection involves membership invitations, accepted using a Blogger Google account, some would be private blog owners decline the suggestion.
That's too complicated for my readers! Can't I just give everybody a password?
But Blogger does not use common passwords.

Some blog owners, who are technically astute, find add on template code, provided by third parties - which demands a password, in a popup window, to continue. This is where their problems start.

The addition of third party supplied JavaScript code, to our blogs, has always been a dodgy process. With third party JavaScript code used to provide password protection against unknown readers, this is even more hazardous to your blog.

This month, we have a blog owner who installed password protection code in his blog template - and subsequently found his blog locked.
I received email saying that my blog has been removed, and has been marked as spam. The email is as follows:
Your blog has been reviewed and confirmed as in violation of our Terms of Service for: MALICIOUS_JAVASCRIPT. In accordance to these terms, we've removed the blog and the URL is no longer accessible.
Can you please review and unlock my blog?

But the story does not end there. Subsequent review of the blog was denied, by Blogger Support.
Your password prompt is not dismissable - and forces users to close their entire browser session, as the Cancel button does nothing. This is malicious behavior, and prevents anyone one on our team from even reviewing your blog content.
This leaves the blog owner with a deleted / locked blog, and no chance of getting the blog back.

Besides the potential threat above, which becomes actual only after spam classification detects the add-on code as malicious, any security expert will recognise two reasons why this solution is worthless.
  1. JavaScript code can be blocked, by any reader with a well implemented security policy.
  2. If not blocked, anybody can view source code and find the "password" right there, in plain sight.
This "solution" is therefore worthless for two reasons.
  1. It is risky.
  2. It does not work.

Why risk loss of your blog, for a risky solution that does not work? There's only one way to protect your blog from unknown readers.
  1. Send each would be blog reader a membership invitation, using the Permissions wizard.
  2. Instruct each reader to open and accept the invitation, using any preferred Blogger account.

>> Top