'Leni Neto' -- Parana, Brazil


You may have received some of these in the last couple of months. Some 'custom financial terms' (when they do it right), followed by a random word, separated by underscores.

There are a few harvest IPs. This one's in Brazil, and has the name 'Leni Neto':

$ whois NET-64-15-139-32-1

CustName: Leni Neto
Address: candido de abreu 107
City: Parana
PostalCode: 83280
Country: BR
RegDate: 2006-05-25
Updated: 2006-05-25

There's also

$ whois

Address: Add2Net, Inc.
Address: Lunarpages Division
Address: 100 East La Habra Blvd.
City: La Habra
StateProv: CA

$ whois

OrgName: Datarealm Internet Services
OrgID: DIS-91
Address: PO Box 1616
City: Hudson
StateProv: WI
PostalCode: 54016
Country: US

and finally

$ whois

OrgName: Big Pipe Inc.
Address: Suite 400
Address: 630 - 3rd Ave. SW
City: Calgary
StateProv: AB
PostalCode: T2P-4L4
Country: CA

I'm guessing the last three are colo for hosting spam content. Anyone in Parana know 'Leni'?

'Digital Infinity Ltd' -- Moscow, RU

A week ago, they harvested my addresses four times on four consecutive days. They then proceeded to attempt to send mail to these ~100 unique addresses around 3000 [update 7/1: 5000] times.

This is a commercial organisation, hosted in the US, registered in Moscow.

The harvesting IPs are all in this small, 14 host netblock:

$ whois NET-208-66-195-0-1

OrgName: Digital Infinity Ltd
OrgID: DIL-32
Address: Ostrovityanova str, 14, 200
City: Moscow
Country: RU

NetRange: -
NetHandle: NET-208-66-195-0-1
Parent: NET-208-66-192-0-1
NetType: Reassigned
RegDate: 2006-05-31
Updated: 2006-05-31

RAbuseHandle: SUPPO189-ARIN
RAbuseName: Support
RAbusePhone: +7 (495) 980-6635
RAbuseEmail: noc@digitalinfinity.org

However, the addresses they're sending from are trojaned home and/or office computers, or their ISP's mail exchangers. I recorded over a thousand unique hosts so far.

And now, data

Preamble complete; now for some data -- or at least, its first derivative; the raw data would compromise my anonymity.

So, I'll have to feed post bits that I deem to be interesting. If you want raw data, make your own once I've made the code available, or convince me via private email that you're not a spammer.

Technical details

A few words follow explaining how the tagged email addresses work. Details have been anonymized.

The tag encodes two 32-bit numbers: Unix epoch time, and the client's ipv4 address. These are concatenated, then encrypted using a standard library. The encryption is not required, but was added due to the initially covert nature of this project. The encrypted binary string is then encoded using base 32. The first implementation used a nearly standard base 64 encoding, but spammers fold case in nearly all instances. Hexadecimal is 80% as efficient as base 32, but as a smaller tag is desirable, a base 32 encoder was written and used.

The resulting tagged addresses look (something) like this:


The 'aa' is an arbitrary prefix and encodes no data. I use a number of different prefixes in each page delivered to increase the number of tagged addresses in the spammers database, as well as gleaning additional information on whether spammers will use all addresses they harvest, and in what order if any.

The above email address, if used, will reveal the exact time and location it was originally harvested from; in this case, the IP address of the local machine, and the UTC time at which I loaded the page earlier today:
2006-06-23 15:07:51

By combining this with the logs from the MTA daemon, we have both harvest and spam data in the same record:

2006-06-23 15:07:51,aa,,2006-06-23 15:09:22,,mailhost.example.org,spam-from@example.org

(that's: time harvested, address prefix, harvest IP, time spammed, spammer IP, spammer HELO, spammer FROM envelope sender)


Around a year ago, I had an idea. Well, I have a few, but this one gained some traction in that it actually produced working code. The code was (is) sloppy and unglamorous, but serves its purpose.

Having placed spamtrap addresses on my website for some years to add to the means of stopping spam from reaching my inbox, I wondered if there was more that I could do with a bait email address. Could the address itself encode information about the host which harvested it? It was obvious that it could, the question was whether I could be bothered to build it. I spent a few hours checking whether this was an old idea -- or at least, one which had been made public -- then did wrote the code.

While spammers are careful to conceal their identities when spamming, often they are less so when harvesting email addresses. Spam from botnet, harvest from home.

I'm doing this anonymously in case I upset any spammers to the point where they could be bothered to pay me a visit. However, I still want to get the data out, so I'll use this blog as a convenient place to do so.