Once again, in a month and a half, Shaw has disabled my outbound email.
For no particular reason.
Oh, sure, the error code says 554, rejected due to poor reputation. So, like before, I do a lookup. (For those interested in the stability of DHCP, my IP address is still the same, a month an a half later. Even after being away for two conferences, and a short vacation.) So, once more, I look up http://www.senderbase.org/senderbase_queries/detailip?search_string=184.108.40.206
This time there is even less information. Google groups, SpamCop, dnsbl.njabl.org, bl.spamcop.net, cbl.abuseat.org, sbl.spamhaus.org, and pbl.spamhaus.org all say I’m clean. (dnsbl.sorbs.net refuses to say anything, oddly.)
RFC-Ignorant.Org does say, again, that Shaw itself is questionable. So, does that mean all Shaw clients are silent tonight? How big of a CIDR does this affect? (And why?) How come I’m the guy who gets picked on?
Once again, Shaw’s “help” “Support” line is of no use. This time around “Jason” tells me I just have to be patient: the spam guys are looking into something. He won’t venture any guesses as to what the something is.
By now people are starting to hear that RSA has been hit with an attack. Reports are vague at best, and we have very little idea how this may affect RSA customers and security in general. But I’d like to opine about a few points.
First, we, in the profession of information security, are still not taking malware seriously enough. Oh, sure, most people are running antivirus software. But we don’t really study and understand the topic. Malware gets extremely short shrift in any general security textbook. Sometimes it isn’t mentioned at all. Sometimes the descriptions are still based on those long-ago days when boot-sector infectors ruled the earth. (Interesting to see that they are coming back again, in the form of Autorun and Autoplay, but that’s simply another aspect of Slade’s Law of Computer History.) Malware has gradually grown from an almost academic issue to a pervasive presence in the computing environment. It’s the boiling frog situation: the rise in threat has been gradual enough that we haven’t noticed it.
Second, we aren’t taking security awareness seriously enough. These types of attacks rely primarily on social engineering and malware. Security awareness works marvelously well as a protection against both. RSA is a security corporation: they’ve got all kinds of smart people who know about security. But they’ve also got lots of admin and marketing people who haven’t been given basic training in the security front lines. For a number of years I have been promoting the idea that corporations should be providing security awareness training. Not just to their employees, but to the general public. For free. I propose that this is not just a gesture of goodwill or advertising for the companies, but that it actually helps to improve their overall security. In the modern computing (and interconnected communications) environment, making sure somebody else knows more about security means that there is less chance that you are going to be hit.
(Third, I really hate that “APT” term. “Advanced Persistent Threat” is pretty meaningless, and actually hides what is going on. Yes, I know that it is embarrassing to have to admit that you have been tricked by social engineering [which is, itself, only a fancy word for "lying"] and tricked badly enough that somebody actually got you to run a virus or trojan on yourself. It’s so last millennium. But it’s the truth, and dressing it up in a stylish new term doesn’t make it any less so.)
It probably hasn’t escaped your notice that there’s a lot of malware/SEO/scamming whenever a major disaster occurs. A few days ago I started to put together a list of commentary (some of it my own) and resources relating to the Japanese earthquake and tsunami, in anticipation of that sort of activity.
Originally, I was using several of my usual blog venues, but decided eventually to focus on one site. As ESET had no monopoly on useful information, I wanted to use a vendor-agnostic site. Actually, I could have used this one, but for better or worse, I decided to use the AVIEN blog, since I’ve pretty much taken over the care and feeding of that organization. The blog in question is Japan Disaster: Commentary & Resources.
It’s certainly not all-inclusive, but it’s the largest resource of its type that I’m aware of. Eventually, it will be organized more so as to focus again on the stuff that’s directly related to security, but right now, given the impact of the crisis, I’m posting pretty much anything that strikes me as useful, even if its relevance to security is a bit tenuous.
I’m afraid I’m going to post this pointer one or two other places: apologies if you trip over it more often than you really want to!
David Harley CITP FBCS CISSP
ESET Senior Research Fellow
I seem to be back on the air.
A few observations over this whole affair:
(Sorry, I’ve not had time to put these in particular order, and some of the point may duplicate or relate …)
1) I still have absolutely no idea why Shaw cut me off. They keep blaming Spamhaus, but the only links they offer me as evidence clearly show that there is no “bad reputation” in the specific IP address that I am currently using, only a policy listing showing one of Shaw’s address ranges.
2) I got absolutely no warning from Shaw, and no notice after the fact.
3) Shaw’s spam filtering is for the birds. Today I got two messages flagged as spam, for no clear reason I could see. They were from a publisher, asking how to send me a book for review. The only possible reason I could see was that the publisher copied three of my email addresses on the same message. A lot of people do that, but it usually doesn’t trip the spam filter. Today it did. (Someone else with Shaw “service” tried to send out an announcement to a group. Since he didn’t have a mailing list server, he just sent out a bunch of messages. Apparently that got *his* account flagged as spamming.) I also got the usually round of messages from security mailing lists tagged as spam: Shaw sure has something against security. And at least one 419 scam got through unflagged today, despite being like just about every other 419 in the world. (Oddly, during this period I’ve noted a slight uptick in 419s and phishing in general.)
4) Through this episode I had contact with Shaw via email, phone, “live chat,” and Twitter. I follow ShawInfo and Shawhelp on Twitter. On Twitter, I was told to send them a direct message (DM). I had, in fact, tried to do that, but Shaw doesn’t accept direct messages by default. (Since I pointed that out to them, they now, apparently accept them from me.) They sent me public messages on Twitter, and I replied in kind. Through the Twitter account they also informed me that error 554 is “poor reputation” and is caused by sending too many emails. They didn’t say how many is too many. (Testing by someone else indicated something on the order of 50-100 per hour, and I’ve never done anything near that scale.)
5) The “live chat” function installs some software on your (the client) machine. At least two of the pieces of software failed the digital signature verification …
6) The “information” I got from Shaw was limited. The first (phone) support call directed me to http://www.senderbase.org/senderbase_queries/detailip?search_string=220.127.116.11 If you read the page, the information is almost entirely about the “network” with only a few (and not informative) pieces about the IP address itself. (I did, separately, confirm that this was my IP address.) The bulk of the page is a report on addresses that aren’t even in the same range as I am. About halfway down the right hand side of the page is “DNS-based blocklists.” If you click the “[Show/Hide all]” link you’ll notice that four out of five think I’m OK. If you click on the remaining one, you go to http://www.spamhaus.org/query/bl?ip=18.104.22.168 At the moment, it shows that I’m completely OK. At the time I was dealing with Shaw, it showed that it’s not in the SpamHaus Block List (SBL) or the XBL. It was in the PBL (Policy Block List), but only as a range known to be allowed to do open sending. In other words, there is nothing wrong with my IP address: Shaw is in the poop for allowing (other) people to send spam.
7) The second (live chat) support call sent me to http://www.mxtoolbox.com/SuperTool.aspx?action=blacklist%3a22.214.171.124+ Again, this page showed a single negative entry, and a whole page of positive reports. The single negative entry, if pursued, went to the same Spamhaus report as detailed above.
8) At the time, both initial pages, if followed through in terms of details, led to http://www.spamhaus.org/pbl/query/PBL164253 giving, as the reason, that “This IP range has been identified by Spamhaus as not meeting our policy for IPs permitted to deliver unauthenticated ‘direct-to-mx’ email to PBL users.” Again, Shaw’s problem, not mine. However, that page has a link to allow you to try and have an address removed. However, it says that the “Removal Procedure” is only to be used “If you are not using normal email software but instead are running a mail server and you are the owner of a Static IP address in the range 126.96.36.199/22 and you have a legitimate reason for operating a mail server on this IP, you can automatically remove (suppress) your static IP address from the PBL database.” Nevertheless, I did explore the link on that page, which led to http://www.spamhaus.org/pbl/removal/ Again, there you are told “You should only remove an IP address from the PBL if (A) the IP address is Static and has proper Reverse DNS assigned to your mail server, and (B) if you have a specific technical reason for needing to run a ‘direct-to-MX’ email service, such as a mail server appliance, off the Static IP address. In all other cases you should NOT remove an IP address from the PBL.” This did not refer to my situation. Unfortunately, THESE TWO PAGES ARE INCORRECT. If you do proceed beyond that page, you get to http://www.spamhaus.org/pbl/removal/form This page does allow you to submit a removal request for a dynamic IP address, and, in fact, defaults to dynamic in the form. It was only on the last part of the second call, when the Shaw tech gave me this specific address, that I found this out. For this I really have to blame Spamhaus.
9) In trying to determine if, by some weird mischance, my computer had become infected, I used two AV scanners, one spyware scanner, and two rootkit scanners. (All results negative, although the Sophos rootkit scanner could have been a bit clearer about what it had “found.”) Of course, I’ve been in the field for over two decades. How would the average user (or even a security professional in a non-malware field) even know that there are different types of scanners? (Let alone the non-signature based tools.)
Well, multiple scanners say I have no malware, no spyware, and no rootkits.
http://www.mxtoolbox.com/SuperTool.aspx?action=blacklist%3a188.8.131.52+ says I’m clean except for Spamhaus.
Spamhaus shows that http://www.spamhaus.org/query/bl?ip=184.108.40.206 I’m clean and it’s Shaw that’s dirty.
Shaw’s support is as inane as ever:
Your representative has arrived.
Stephen – 6685 (11:43:37):
Thank you for choosing Shaw Internet Chat Support, my name is Steve. I will be happy to help you today.Before continuing, would you please confirm your home telephone number and address so that I can bring up your account information?
[If you don't mind, I've elided this, but it's the only change I've made - rms]
Stephen – 6685 (11:44:57):
Thank you, one moment please
Stephen – 6685 (11:48:07):
from what we see on the notes, it looks like your email is being blocked to due a poor reputation which means its being blocked by spam protection companies, im just looking into this a little further for you.
Rob Slade (11:49:16):
Do you have any idea of what that means? When I talked to “Rowell” yesteerday, he did not know anything about anti-spam technology, and just kept handing me bafflegab. If you do not have any knowledge in thsi area, please hand me to someone who does.
Rob Slade (11:49:46):
I should let you know that I *do* know what I’m talking about: look up “Robert Slade” on Wikipedia.
Stephen – 6685 (11:49:48):
your being blocked by spamhaus
Stephen – 6685 (11:50:02):
Rob Slade (11:50:18):
I’ve written two books on viruses and malware, the first book on software forensics, and a dictionary of information security.
Rob Slade (11:50:38):
I do know what spam is, and I am well aware of antipsam technology.
Rob Slade (11:51:08):
Per looking at senderbase yesterday, my specific IP address has nothing on it. Just Shaw’s domain range.
Stephen – 6685 (11:52:03):
you would need to go here http://www.spamhaus.org/lookup.lasso type in your ip address to lookup, then click the document it shows under the listed in red, and follow the steps to get it removed from spamhaus
Rob Slade (11:52:29):
Rob Slade (11:53:04):
See that it is only listed in the PBL, and if you look up the detail on that you will see that it is only the Shaw /22 range, and not my address.
Rob Slade (11:53:49):
Going back to your original list, you will see that it is *only* listed on Spamhaus (and therefore only on the PBL), and that *all* the other sites give me a clean bill of health.
Rob Slade (11:54:19):
In addition, why did I get absolutely no warning or notice from Shaw, just had my ability to send cut off without warning?
Stephen – 6685 (11:54:27):
its not blocked by us
Stephen – 6685 (11:54:31):
thats why we couldnt give warning
Stephen – 6685 (11:54:37):
its blocked by spamhaus
Rob Slade (11:54:49):
It is your SMTP server that refuses the connectionh.
Rob Slade (11:55:00):
You can’t blame Spamhaus.
Stephen – 6685 (11:55:14):
http://www.mxtoolbox.com/SuperTool.aspx?action=blacklist%3a220.127.116.11+ please review this, it will show you based on a search of your ip address, its listed by spamhaus-zen….
Rob Slade (11:55:52):
That is the same list as before.
Stephen – 6685 (11:56:19):
yes it is
Rob Slade (11:56:36):
As I told you, it gives me a clean bill of health, except for Spamhaus, and Spamhaus only lists the Shaw /22 range in the PBL, not my IP address specifically.
Stephen – 6685 (11:56:37):
if you look at the top.. spamhaus-zen to the right of that it shows as listed which means its blocked by them
Stephen – 6685 (11:57:00):
its still being listed by them, otherwise it would come up saying OK next to spamhaus
Stephen – 6685 (11:57:16):
if you login to webmail and try sending an email out from there, it will work because its not associated with your computer
Stephen – 6685 (11:57:30):
its not working on your computer because your ip address is blocked by spamhaus
Rob Slade (11:57:44):
Yes, and if you look at the detail, you will see that I am *not* lsited in the SBL, *not* listed in the CBL, and *only* listed in the PBL, and if you look at the detail for *that* you will see that it is *Shaw* that violates, not me.
Rob Slade (11:58:37):
Here. chew on these: http://is.gd/VbjOIh http://is.gd/ogefIX
Stephen – 6685 (11:59:31):
im not sure what i am suppose to be seeing in those links.. Error establishing a database connection
Stephen – 6685 (12:00:07):
http://www.spamhaus.org/pbl/query/PBL164253 from there, you will need to follow the steps from clicking on remove an ip from pbl
Rob Slade (12:01:20):
In the meantime, I will be writing up more blog posts on how Shaw has inconsitent spam filtering, does not say what kind of spam filtering it does do, has a weird relationship with the blacklisting outfits.
Rob Slade (12:02:09):
Obviously you have not read the page you sent me. This is the procedure only if you are running an email server (MTA) yourself. I don’t. You guys do.
Stephen – 6685 (12:05:15):
yes, from the report, its showing that its being blocked due to not using smpt authentication, that gets addressed from our side, where we communicate with spamhaus to get that resolved, however also by having you follow the link from the remove my ip address can usaully help get it resolved quicker.
Stephen – 6685 (12:06:12):
it is blocked by spamhaus, not us, which is something that will get looked into, if it was just being blocked by us, we could easily resolve it for you, however because its being blocked by a 3rd party, it will take some time, in the meantime you can use webmail to send and receive emails
Rob Slade (12:06:19):
How so? I don’t run an SMTP server, so I can’t give them full info in filling out that form.
Rob Slade (12:07:06):
Besides, it’s not a static address.
Rob Slade (12:07:45):
Obviously you do not know what you are talkign about. Are you going to put me through to someone who does?
Stephen – 6685 (12:08:08):
yes i do know what i am talking about Rob
Rob Slade (12:08:45):
Then how come you are asking em to fill out a form when the instructions specifically state not to do it unless this is a static IP address and I am running my own mail server?
Rob Slade (12:09:36):
http://www.spamhaus.org/pbl/removal/ “You should only remove an IP address from the PBL if (A) the IP address is Static and has proper Reverse DNS assigned to your mail server”
Stephen – 6685 (12:09:37):
i am just looking to see what more we can do on this right now, i will be a couple minutes.
As noted, Shaw is not very helpful with spam. I’ve been getting spam from Marlin Travel, and from a band of people selling recuriting seminars, for a number of years. I have been reporting this spam (to Shaw, and their supposedly automated spam filters) on at least a weekly basis for years. Occasionally they deign to mark one of the messages as spam, but not on anything like a consistent basis.
Spam filtering is not transparent. You can turn it on, or off. You can have the spam go to the bit bucket, or get flagged. There are no other options, and you have no information on how it works (or doesn’t). (Heck, Vancouver Community Net [formerly Free-Net] does better than that.)
On my non-support call with Shaw, the agent did correctly identify the IP address I am (currently) using. I have no idea when last it was switched. Looking it up on senderbase is not supremely informative: there doesn’t seem to be any information on the address itself, other than the fact that it’s not in the SpamHaus Block List (SBL) or the XBL. It is in the PBL (Policy Block List), but only as a range known to be allowed to do open sending. In other words, there is nothing wrong with my IP address: Shaw is in the poop for allowing (other) people to send spam.
Meantime I have confirmed that, as I already knew, there is nothing malware or spam related on my machine. Nothing that MSE detects. Nothing that Vipre detects. Nothing that Spybot detects. At the moment I’m running the Sophos rootkit detector, and F-Secure’s Blacklight. They haven’t found anything either. I am, of course, morally certain that Shaw was lying to me about the possibility, but, unlike them, I’m not arrogant enough not to check. I was right: they are idiots. And, with their non-support, have cost me a lot of valuable time checking a clean machine. (Plus not providing the Internet service I’m paying for.)
I have had Internet access with Shaw Cable for a number of years. I have been using the same system for at least seven years. I’m a malware researcher, so I check my machines thoroughly and regularly.
I also know that Shaw has a very bad reputation in terms of spam. There are a number of systems that I cannot send email to, since Shaw connected computers, apparently, send a lot of spam and viruses. I also know that I spend a significant amount of time every day trying to tune Shaw’s very crude spam filtering: identifying and sending them messages they have tagged as spam which are not, and sending them messages they have not tagged which are spam.
Today my wife found she couldn’t send email. When I tried, I couldn’t either. We are getting a message from the SMTP server #554, which has something to do with poor reputation.
I did manage to send email through Webmail, and so sent a message to Shaw’s technical support. (Finding out, when I did so, that they changed the technical support email address in December, without telling anyone.) They responded about three hours later. Rowell, the person making the call, blamed everything on senderbase.org. Rowell denied that this had anything to do with blacklisting. He also denied that he was saying that my computer was sending any spam. He said that if I did not send any email for the next two days, that would fix the problem. He refused to say why there was any indication that my computer was in any way at fault, or offer any evidence that I was sending out spam or viruses. He also refused to escalate the problem to anyone who was either higher up and could do anything, or anyone who had any technical knowledge about the problem.
Shaw is now in my dirty words file.
Despite what Dilbert Comic Strips may teach you, our job as security professional is to enable information services – not prevent them.
The bad guys do evil: we try to prevent it (or clean-up after) so that users can continue and use systems as if there is no evil in the world. If IT security had a Hippocratic oath, it would probably be along those lines.
Here’s a recent example. This morning I got a call from my credit card company asking me if I’d done some transactions that seem suspicious. I hadn’t, and so they will cancel the transactions (and unfortunately, cancel my credit card and send me a new one). I’m not going to stop using my credit card, and will probably completely forget about this incident. I didn’t lose any money, and the inconvenience was minimal: this is all thanks to the people that chase up the credit card fraud and enable customers around the world to use their cards despite countless attacks on credit card users, some (as my example shows) successful.
Things are not so simple in the email war front. When SMTP was introduced, it described a simple, reliable, scalable system for communication. Almost 30 years after that, we stripped email of some of its most important features. By we, I mean the IT security world. In fact, we’re slowly doing to SMTP what TSA is doing to air travel.
First, the major feature of SMTP: sending and receiving emails. This is probably our biggest failure today: There is no guarantee you will be able to send or receive emails. In fact, if you communicate with the external world, it is almost guaranteed that you will not receive a certain percentage of your emails, and that some emails you send will not arrive. Sure, there are legitimate reasons: we need to protect from spam, viruses and phishing. But the bottom line is that SMTP was designed to reliably deliver an email from point A to point B. Today, we send an email and then call to verify it was received (or send a second email which mysteriously arrives after the first one was blocked).
Next, we kill useful SMTP features. Remember the days when you got an email ‘bounce’ when mistyping the email recipient’s address? Forget about it; those days are long gone. I’m not sure what Spamcop’s exact mission statement is, but it might as well be “make email unuseful”. They have outlawed email bounces (which, by the way, are required by the SMTP RFC) and continued to take out all auto-responders.
Remember read-receipt? Gone. The postal service had this feature in 1841, but we can’t have it in 2010. Do you want to know if a certain email exists? You can’t. Want to send email directly from your computer without using a mail relay? A non-starter. Ever heard of email fragmentation? This is an awesome feature of SMTP but don’t waste time learning it – it won’t work on the Internet today (and this time we share some of the blame).
Look at HTTP. You click on a link, and you get to the page. If you get an error, you know it’s the web site’s fault. An attack on NCSA’s httpd server is one of the first documented buffer overflow attacks, and yet attacks on modern HTTP servers are practically non-existent. SQL injection and XSS are everywhere and yet users surf dynamic pages all the time without being blocked. We’re doing a good job fixing up HTTP without being a “Mordac”. Too bad we couldn’t do it with SMTP.
Is there hope for SMTP? I think there is. Last decade the doctors were ready to pull the plug on email: spam and viruses were so frequently in the users’ inbox that email was on the verge of being unusable: You had to spent a noticeable percentage of your day clicking the ‘del’ button. These days are over: you rarely see spam in your inbox today, and if you’re like me, you get more irritating chain letters from family members you can’t block (hi mom) than shady ads for pills.
This war can be won. We just need to remember the Hippocratic oath for the IT security world and enable reliable communication again.
Here’s a weird spam I got last night:
The route taken through Customs is mainly determined by your point of departure and whether you are bringing into the country more duty payable goods than your free allowance. For those passengers who have flown in from outside the European Community (EC), their baggage will have a white tag and they must pass through either the Red or Green channel according to the amount of duty free goods they have. Those passengers arriving from countries within the EC should use the Blue channel, and their baggage will have green-edged tag.
As part of our routine check and based on the above, we have a consignment in your name; you are advised to come to the office address below
You are required to come with the following:
1. Your ID
2. Diplomatic Tag either white or green-edge tag.
3. Non Inspection document
Your appointment time is 10am GMT, failure to comply; we will have over the matter to Metropolitan and the FBI. I am the officer in charge of your matter.
It’s weird, because it contains no advertisement, and no links. There’s nothing “encoded” in it - it seems to be an old version of this notice.
So why would a spammer waste valuable botnet cycles on sending me the email? The only explanation I could come up with is “a boy who cried wolf” attack. You send this email a few times, and the Baysian filtering systems train themselves that this is a good email (i.e. “ham”). Most Baysian spam filtering systems have a loopback mechanism where spam email is used to train the system further, and ham email is used to teach the system what “good” email is. If this email is seen a few times and considered ham, spam filters will accept something similar to it that contains a link. That link, can be the spam or phishing attack.
Another guess is that it’s simply used to verify email addresses – you read that a scary Customs agent from Heathrow wants you in his office first thing tomorrow morning, and you quickly reply to ask what it’s about; the spammer (whose reply-to address is different than the “From”) gets a confirmation that your email address is valid, maybe with some more details like your phone number. This is a plausible explanation but it seems like too much hard work just to get some valid email addresses.
Any other guesses?
I am a bit freaked.
Last month I received an email message from American Express. I very nearly deleted it unread: it was obviously phish, right? (I was teaching in Toronto that week, so I had even more reason to turf it unread rather than look at it.)
However, since I do have an Amex card, I decided to at least have a look at it, and possibly try and find some way to send it to them. So I looked at it.
And promptly freaked out.
The phishers had my card number. (Or, at least, the last five digits of it.) They knew the due date of my statement. The knew the balance amount of my last statement.
(The fact that this was all happening while I am aware from home wasn’t making me feel any more comfortable with it …)
So I had a look at the headers. And couldn’t find a single thing indicating that this wasn’t from American Express.
(I had paid my bill before I left. Or, at least, I *thought* I had. So I checked my bank. Sure enough, that balance had been paid a couple of days before. However, I guess banks never actually transfer money on the weekend or something …)
A couple of days later I got another message: Amex was telling me that my payment was received. That’s nice of them. They were once again sending, in an unencrypted email message, the last five digits of my card number, and the last balance paid on my account.
Well, I figured that it might have been an experiment, and that they’d probably realize the error of their ways, and I didn’t necessarily need to point this out. Apparently I was wrong on all counts, since I got another reminder message today.
Are these people completely unaware of the existence and risk of phishing? Are they so totally ignorant of online security that they are encouraging their customers to be looking for legitimate email from a financial institution, thus increasing the risk of deception and fraud?
Going to their Website, I notice that there is now an “Account Alerts” function. It may have been there for a while: I don’t know, since I’ve never used it. Since I’ve never used it, I assume it was populated by default when they created it. It seems to, by default, send you a payment due notice a week before the deadline, a payment received notice when payment is received, and a notice when you approach your credit limit. (Fortunately, someone had the good sense not to automatically populate the option that sends you your statement balance every week.) These options may be useful to some people. But they should be options: they shouldn’t be sending a bunch of information about everybody’s account, in the clear, by default.
(There are, of course, “Terms and Conditions” applicable to this service, which basically say, as usual, that Amex isn’t responsible for much of anything, have warned you, and that you take all the risks arising from this function. I find this heavily ironic, since I knew nothing of the service, don’t want it, and got it automatically. I never even knew the “Terms and Conditions” existed, but in order to turn the service off I’ll have to read them.)
(In trying to send a copy of this to Amex, I note that their Website only lists phone and snailmail as contact options, you aren’t supposed to be able to send them email.)
Here’s something that’s been bugging me for a while. Twitter is a very open platform – there are probably hundreds of “entry points” through various APIs and clients. It is also very simple – which is what makes it powerful; basically you put your text into their database, and others view it according to a search they do (either explicitly, or implicitly – by following you or monitoring for @ replies).
So given this wealth of entry points, and simplicity, why aren’t we seeing twitter flooded with spam? I’m not talking about the occasional spammer following you in hopes that you follow them back and get exposed to their spam – I’m talking about a massive spam attack including your twitter name (so it shows when you look for @ replies), including hash tags for all trending topics, and generally – flooding twitter at the rate we are seeing with email messages?
After all, the multitude of entry points makes it more difficult to block it from entering than email, and the simplicity of the protocol makes it difficult to filter or block.
I know the twitter team is putting efforts into blocking and filtering spam, but I find it hard to believe they are successfully blocking virtually all spam attacks. Spammers tend to be sophisticated, and I’m pretty sure they watch Opera, too – they must know what twitter is.
Am I missing something?
It seems I get this IN MY INBOX everytime I post…
We have received your request to join the puitika
group hosted by Yahoo! Groups, a free, easy-to-use community service.
This request will expire in 7 days.
TO BECOME A MEMBER OF THE GROUP:
1) Go to the Yahoo! Groups site by clicking on this link:
(If clicking doesn’t work, “Cut” and “Paste” the line above into your
Web browser’s address bar.)
2) REPLY to this email by clicking “Reply” and then “Send”
in your email program
If you did not request, or do not want, a membership in the
puitika group, please accept our apologies
and ignore this message.
Yahoo! Groups Customer Care
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
I received this email today:
I inform you about site http://carder.su where people trade in stolen credit cards. As i’m a holder of visa classic i’m sincerely
exasperated at appearing such sites in your hosting. I beg of you to take strong measures and don’t be indifferent to heart-break of other people. This complaint will be sent to the FBI.
Best regrads, Jon Shirov.
At first I was shocked, why would someone allow such a site to still be up even though someone reported it to the FBI. I had to do something.
Rushing to the rescue I looked at the site and it appears to be a pretty straight forward scam-sell site, you come there and buy stolen goods.
Why have I been notified only now I wondered… I looked back in my spam log and what do you know the same email appears more than once in my spam folder with different names, dates and of course email addresses
I am not sure what the scam/spam’s purpose is, apparently they want you to go to their site and see what they have to offer – you might be a potential customer to their operation.
I of course didn’t dig in to the site, nor am I interested in buying anything found there – on the other hand I will also not report this to the FBI as the site is not hosted inside the United States (It is hosted in Russia), nor is its domain under a US registrar (ends with a SU).
Whoever knows of a place to report such sites to please let me (us) know.
Emails from seemingly no where and from no one trustworthy.. haha
Manish from this side, i have a good hacking project on linux machine, configuration are below: please considue and if u are able to hack this system our company can pay whatever u want. or creat custom exploit that provide reverse shell . this server is online [ip address will be dilivered after project accepted by you] after u hack this system u just provide screen shot of any email header from any user on this server…I am sending you some details that are helpful for you.
Linux 2.6.18, sendmail: 8.13.1, apache 2.0.52, and open webmail 2.52
Suspected open ports:
25, 111(rpc), 443, 1720(SIP), 870(unkwon), 80, 79(finger), 110(pop), 143(imap),
and system is protected by firewall have ttl of system is: 53
Network distance: 10 hops.
Send me mail if u are ready to accept this challenge with project cost and time, so after i send IP address of live server, and money will be dilvered by Wire of paypal or bank transfer, any option that u want.”
A short list of legitimate emails you will never get, if you have something else feel free to add:
* Lottery winnings – Microsoft is the big winner here, they keep sending me winning notifications, but I just don’t collect
* Your doctor’s prescription (probably some obscure medicine might go through, while most won’t) – to buy “cheap” fake medicine
* Your Antivirus renewal notice – trying to get you to install some form of malware
* Your bank’s security notice, and statement – of course its phishing scams
* Paypal payments being done to your name or from your name – phishing scams mainly
* Job offers – I get these money “mule” offers and get paid per call spam
Anything I missed?