I got an amusing little piece of email spam this morning.
Amusing, that is, from the point of view of someone who likes to figure out what the spammers are doing and what they’ve compromised in order to do it. Here’s the message, as displayed to me in gmail (I’ve inserted spaces in the URL and email addresses, so your browser won’t make them clickable):
from McDonald’s Survey Department. <survey @ mcdonalds.com>
reply-to survey @ mcdonalds.com
date Mon, Sep 27, 2010 at 15:01
subject McDonald’s Survey
Please give us only 5 minutes of your valuable time to ask you some questions about our products . Please be aware that we will not ask you about any personal information.
In return, we will credit $90.00 to your account - just for your time.
If you want to answer our simply 8 questions , please click the link below :
Thank you for helping us to become better .
Sincerely, McDonald’s Survey Department.
Please do not reply to this email. This mailbox is not monitored and you will not receive a response.
Of course, the message isn’t really from anyone at mcdonalds.com, but you knew that.
The first interesting thing is the URL. As is often the case with spam URLs, they’ve tried to make it look like a legitimate URL from the company by sticking their domain name in there somewhere — in this case, it’s after the slash, and one has to know how to read URLs to understand that putting it there just makes it information that’s passed to the web server, and has nothing to do with what web server gets used.
And the web server it’s pointing us to is at uri.edu, which is what piqued my interest. This isn’t some throwaway domain, nor anything else registered by the spammer, but something residing at the University of Rhode Island. In particular, this looks like a temporary name assigned to some computer connected to U of RI’s network.
My guess is that a student machine was compromised — malware got installed on it — and the malware set up a hidden web server that’s meant to handle these requests.
Let’s look at where the email message really came from, by checking out the
Received lines in the headers. Here are the two operative ones:
Received: from www-7419bfef271.modrsoft.com ([188.8.131.52])
by hormel7.ieee.org (8.13.8/8.13.8/Debian-3)
with ESMTP id o8S55UDI020590; Tue, 28 Sep 2010 01:05:32 -0400
Received: from User ([184.108.40.206]) by www-7419bfef271.modrsoft.com
with Microsoft SMTPSVC(6.0.3790.4675); Tue, 28 Sep 2010 02:41:35 +0800
Reading bottom up, the message was submitted by an IP address in SBC Internet Services, to an IP address at Modrsoft, a legitimate service provider in China. The spammers appear to have found an open relay in Modrsoft’s network, or else Modrsoft doesn’t block port 25, and they compromised a machine there, as well.
Here’s what it looks like:
- A compromised computer on SBC’s network was ordered to submit the spam message.
- It submitted it to a compromised computer on Modrsoft’s network.
- That computer relayed the message to its recipients (including me).
- The message directs users to a clandestine web server on a compromised machine at University of Rhode Island.
Unfortunately, the trail goes cold there: I tried to snag the web page, to see what it’s meant to do... but I can’t contact a web server at that address. The machine has been taken offline, has a new address, or has been cleaned up. In any case, it’s not serving the bad guys at the moment. That’s often true of these things: they may only work for a brief time, but they can certainly do their work in that time. They might do the dirty work directly, or redirect you to another web server that will.
Probably, visiting that web site with a susceptible browser (or user) would result in the installation of malware on the visiting computer, adding it to the zombie network. In addition, they’re offering $90
to your account for participating, so they’ll obviously be asking you to give them some sort of account information where they can deposit the money — an account they’re actually be sucking dry as soon as they have access to it.
Too bad I didn’t get to it soon enough, to see for sure what the web page is trying to do.