Spam level dips


Spam level dips

Warwick Ashford

The recent decline in global spam was the result of a halt in the spam-sending activities of three botnets and unrest among pharmaceutical spam-sending gangs, Symantec's latest MessageLabs Intelligence Report has revealed.

In the two weeks after 25 December, spam volumes declined 58% from 80.2 billion spam emails a day to 33.5 billion, reminiscent of declines experienced when California-based ISP McColo was taken offline in late 2008.

The report noted a decline in the Rustock, Lethic and Xarvester botnets, although in the two weeks that Rustock was dormant, it was being used for click-fraud to generate fake referrals for click-through expenses.

"The closure of spam affiliate Spamit was partially responsible for the disruption to spam output," said MessageLabs Intelligence senior analyst, Paul Wood,

"However, there are likely other factors at work, such as consolidation and restructuring of pharmaceutical spam operations, which has led to instability in the market likely to be exploited as a business opportunity by other spam gangs. We expect to see more pharmaceutical spam in 2011 as new pharmaceutical spam brands emerge and botnets compete for their business," he said.

Since the end of 2010, MessageLabs Intelligence has seen shifting patterns related to pharmaceutical spam-sending, the report said.

Previously, the Canadian Pharmacy brand was the most prolific of the pharmaceutical spam brands. However, when Spamit shut down in October 2010, the brand disappeared as affiliates switched to sending spam for other brands.

Email Alerts

Register now to receive IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

COMMENTS powered by Disqus  //  Commenting policy