Skip to main content

Do spammers fear OCR?

Nick FitzGerald recently sent me two sample spams that seem to indicate that some spammers fear that using images in place of words isn't enough. They've started to obscure their messages to prevent optical character recognition.

The first spam appears to be a scan of a document that's been skewed slightly. Now this could be a simple and bad scan.



But the second is even more interesting. It appears to be perfectly normal:



Until you look at the fact that this was actually constructed using <DIV> tags for layout and the breaks between the lines are in the middle of words. Here Nick has kindly inserted borders showing that the words are broken horizontally and then put back in the right position:



But is anyone doing OCR, or are spam filters getting good enough that the spammers are being really paranoid about what they are sending?

The funny think about the second example is that the URL they include is not obfuscated, is clickable and appears in the SURBL :-) So despite the effort to obscure the content a simple check of the spamminess of the URL gets this email canned.

Comments

Justin Mason said…
That *is* interesting!

Typically, when I've seen something like this before, it indicates that one of the proprietary services (AOL? GMail?) is indeed using OCR, and I just didn't know it yet -- but the spammers do.
Nick also mentioned another, non-OCR, possibility for doing this... if the images are skewed or split in different ways over time then the spammer prevents a spam filter from being able to track a common hash for each image.
mr g said…
On the other hand, most e-mail clients (even webmail services) do not show images by default, so what's the point of using images?

If I get such an e-mail, it'll probably land in my Junk E-mail. If it does not, it will be a blank e-mail with image placeholders.

Or am I missing something here?
Anonymous said…
"... most e-mail clients (even webmail services) do not show images by default, so what's the point of using images? ... Or am I missing something here?" -- mr g

I think what you missed is that, by default, the _most used_ Email clients do show inline HTML images from MHTML format messages that use the cid: protocol to reference those images. Perhaps only 80% of all potential recipients and only 7% of potential recipients who are *nix users will see the spam's graphical ad, but that really does not matter to the spammer, and matters even less if this new approach means that each week s/he gets a few hundred million more ads past the filters until they are further tweaked.

Of course we don't know if this is more successful or not, BUT the spam-trap address that snagged both the samples John referred to is still getting a goodly amount of the "skewed scan" style of "junk shares" spam so maybe that tells us something?
Anonymous said…
"But is anyone doing OCR, or are spam filters getting good enough that the spammers are being really paranoid about what they are sending?" -- jgc

Well, back in January, I think the answer was no-one was doing OCR, although there had been some talk about it. However, on 14 April 2006, Martin Blapp posted a link to his "Image validator/OCR SA plugin" for Spamassassin, to the MIMEDefang (and other??) lists. An archived copy of that mesage is at:

http://lists.roaringpenguin.com/pipermail/mimedefang/2006-April/029999.html
Sorin said…
They went even deeper in this anti-ocr issue. Now they send emails with an image inside which is created from multiple parts. The parts seem to be created with a generator.

See an email here:
http://www.mustaca.de/blog

Popular posts from this blog

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it:


Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name.

There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly.

What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message:

Our system is unable to process last names that contain non-letters, please replace them with spaces.

Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your last name …

All the symmetrical watch faces (and code to generate them)

If you ever look at pictures of clocks and watches in advertising they are set to roughly 10:10 which is meant to be the most attractive (smiling!) position for the hands. They are actually set to 10:09.14 if the hands are truly symmetrical. CC BY 2.0image by Shinji
I wanted to know what all the possible symmetrical watch faces are and so I wrote some code using Processing. Here's the output (there's one watch face missing, 00:00 or 12:00, because it's very boring):



The key to writing this is to figure out the relationship between the hour and minute hands when the watch face is symmetrical. In an hour the minute hand moves through 360° and the hour hand moves through 30° (12 hours are shown on the watch face and 360/12 = 30).
The core loop inside the program is this:   for (int h = 0; h <= 12; h++) {
    float m = (360-30*float(h))*2/13;
    int s = round(60*(m-floor(m)));
    int col = h%6;
    int row = floor(h/6);
    draw_clock((r+f)*(2*col+1), (r+f)*(row*2+1), r, h, floor(m…

Importing an existing SSL key/certificate pair into a Java keystore

I'm writing this blog post in case anyone else has to Google that. In Java 6 keytool has been improved so that it now becomes possible to import an existing key and certificate (say one you generated outside of the Java world) into a keystore.

You need: Java 6 and openssl.

1. Suppose you have a certificate and key in PEM format. The key is named host.key and the certificate host.crt.

2. The first step is to convert them into a single PKCS12 file using the command: openssl pkcs12 -export -in host.crt -inkey host.key > host.p12. You will be asked for various passwords (the password to access the key (if set) and then the password for the PKCS12 file being created).

3. Then import the PKCS12 file into a keystore using the command: keytool -importkeystore -srckeystore host.p12 -destkeystore host.jks -srcstoretype pkcs12. You now have a keystore named host.jks containing the certificate/key you need.

For the sake of completeness here's the output of a full session I performe…