Risk
5/27/2009
02:24 PM
Keith Ferrell
Keith Ferrell
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Spam Surge: 9 Out Of 10 E-mails Can't Be Good!

90% of all email was spam last month, according to Symantec's MessageLabs Intelligence Report, just released. The figure is up more than 5% in the last month. Good news, I guess, is that things can't get much more than 10% worse from here.

90% of all email was spam last month, according to Symantec's MessageLabs Intelligence Report, just released. The figure is up more than 5% in the last month. Good news, I guess, is that things can't get much more than 10% worse from here.The new MessageLabs Intelligence Report quantifies a number of trends, measured in April traffic, that give some insight into how the spammers are coming at us:

Spam runs on U.S. time: Spam levels peak in the U.S. between 9am and 10am, local. MessageLabs' conclusion is that either the most active spammers are based in the U.S., or that that first full hour of the workday is when recipients are likeliest to respond. My guess -- and it is a guess -- is that it's the latter; people settling in to work may be easier marks while the first cup of coffee is still warm than later in the day when they're preoccupied with other (one hopes more work-related) demands.

CAPTCHA can't catch 'em: The number of effective CAPTCHA-cracking tools is letting the spammers get around the random letter/number tests designed to keep spammers from getting around them; hence, the sharp increase in the number of phony social network and webmail accounts the spammers are creating. The report suggests that new, tougher CAPTCHA-esque technology on the horizon is driving spammers to CAPTCHA while the CAPTCHA-ing is good. Botnets are the base: Close to 60% of spam was botnet-generated, with the three most active bots accounting for more than a third of spam.

Social nets net spam: No news here that social networks, and free mail services are prime targets for address harvesting and malicious link distribution.

As I said at the outset, the spam situation, statistically, can't get much worse.

Bur of course it doesn't have to.

The complete MessagLabs Intelligence Report for May, 2009 can be downloaded here.

Looking to keep security high and security expenditures low? Check out bMighty bSecure SMB Security On A Budget, now available on-demand.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.