[Spambayes] Exceptionally well-done identity-theft spam
tim.one at comcast.net
Mon Dec 29 19:34:59 EST 2003
> I wonder whether this is not the face of things to come --
> reliable-looking links to reliable-looking websites, where the HREF
> actually points elsewhere.
For identity-theft scam spam, almost certainly -- they have to trick you
into revealing personal info you wouldn't normally pass out. But if what
you got after clicking on the link was, e.g., an offer to cut your mortgage
rate, or to enlarge part of your anatomy, I expect the response rate would
be too low to repay the costs. After all, the initial sales msg flat-out
lied to you then, and the percentage of people eager to get fleeced a second
time has got to approach 0.
> Note in the source code that the incriminating part of the URL in
> the HREF (and in the browser window that opens) is coded in Hex
> values rather than characters.
> My guess is that if you dump enough of these messages into your Junk
> folder, Spambayes will be smart enough to identify this kind of URL
> as a high-probability token. Spambayes developers, am I right? Will
> too many % signs in a URL raise the spam probability?
Not now, unless you save away an enormous number of these things. We break
URLs into pieces based on the official separator characters now, but that's
it. The specific scam in question generated these distinct URL-related
It would *probably* work well to, in addition, generate
for each instance of a % escape. That needs testing, though, as "pure wins"
are almost non-existent in this game, and for all I know some church in Iowa
generates HTML parish newletters in which all URLs are encoded just because
someone didn't understand an option in their HTML-generating software.
More information about the Spambayes