Risk
5/25/2011
01:22 PM
Connect Directly
RSS
E-Mail
50%
50%

3 Banks Service Majority Of Spam-Driven Sales

95% of spam-advertised products are monetized using merchant services from just a handful of banks, suggesting payment handling is the weak link in the global spam value chain.

The majority of the world's spam-driven sales are serviced by just three banks.

That surprise finding comes from a new paper that literally "follows the money" for global spam. The paper, to be delivered at next week's IEEE Symposium on Security and Privacy 2011 in Oakland, Calif., is credited to 15 researchers from four institutions--the University of California at Berkeley, University of California at San Diego, the International Computer Science Institute, and Budapest University of Technology and Economics.

Interestingly, their research takes a different tack from most spam studies, which largely focused on how spam is distributed. Today, that's largely via botnets. "While most attention focuses on the problem of spam delivery, the email vector itself comprises only the visible portion of a large, multi-faceted business enterprise," said the researchers.

In fact, the so-called "spam value chain" involves numerous components, including not only botnets, but also domain registration, name server provisioning, hosting services, and proxy services. But spammers must also process orders, which requires "payment processing, merchant bank accounts, customer service, and fulfillment."

To see how these components work together, the researchers studied three months of real spam data, gleaned from captured botnets, spam feeds, and URLs advertised via spam--among other sources. From there, they grouped spam operations into three broad categories: counterfeit software, fake luxury goods, and pharmaceuticals. Finally, they made more than 100 purchases from spam-advertised sites, gathering further data about everything from the merchant banks they used to their and fulfillment operations.

As a result of their analysis, the researchers said that one of the principle weak links in the spam value chain is payment handling. In fact, "95% of spam-advertised pharmaceutical, replica, and software products are monetized using merchant services from just a handful of banks," they said.

All told, they saw 13 banks handling 95% of the 76 orders for which they received transaction information. (Only one U.S. bank was seen settling spam transactions: Wells Fargo.) But just three banks handled the majority of transactions: Azerigazbank in Azerbaijan, DnB NOR in Latvia (although the bank is headquartered in Norway), and St. Kitts-Nevis-Anguilla National Bank in the Caribbean. In addition, "most herbal and replica purchases cleared through the same bank in St. Kitts, ... while most pharmaceutical affiliate programs used two banks (in Azerbaijan and Latvia), and software was handled entirely by two banks (in Latvia and Russia)," they said.

Surprisingly, all software orders and 85% of pharmaceutical orders used the correct Visa "Merchant Category Code," which identifies what's been sold. "A key reason for this may be the substantial fines imposed by Visa on acquirers when miscoded merchant accounts are discovered 'laundering' high-risk goods," said the researchers.

Meanwhile, orders were fulfilled from 13 suppliers in four countries: the United States--Massachusetts, Utah, and Washington, all for herbal purchases, as well as West Virginia for pharmaceuticals--plus India, China, and New Zealand. Most pharmaceuticals came from India, while most herbal products came from the United States, likely due to weak regulations, they said.

So, what's the next step? To help stop spam, the researchers suggest targeting the related payment infrastructure, since options are few and switching costs high. In particular, they suggest that U.S. issuing banks should refuse to settle "card not present" transactions for items from known-spammers, given that with a bit of undercover work, keeping tabs on said spammers doesn't appear to be too difficult. Furthermore, at least where pharmaceuticals and counterfeit software is concerned, there may already be a legal basis for blocking transactions.

"We note that a quite similar action has already occurred in restricting U.S. issuers from settling certain kinds of online gambling transactions," they said.

Some type of legal change, however, may be required to get U.S. issuing banks to comply. "Spam is actually very profitable for the banks and credit card companies that move the money. That might affect how likely they are to actually do something about this," said Mikko Hypponen, chief research officer at F-Secure, in a related blog post.

In this new Tech Center report, we profile five database breaches--and extract the lessons to be learned from each. Plus: A rundown of six technologies to reduce your risk. Download it here (registration required).

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-2014-0640
Published: 2014-08-20
EMC RSA Archer GRC Platform 5.x before 5.5 SP1 allows remote authenticated users to bypass intended restrictions on resource access via unspecified vectors.

CVE-2014-0641
Published: 2014-08-20
Cross-site request forgery (CSRF) vulnerability in EMC RSA Archer GRC Platform 5.x before 5.5 SP1 allows remote attackers to hijack the authentication of arbitrary users.

CVE-2014-2505
Published: 2014-08-20
EMC RSA Archer GRC Platform 5.x before 5.5 SP1 allows remote attackers to trigger the download of arbitrary code, and consequently change the product's functionality, via unspecified vectors.

CVE-2014-2511
Published: 2014-08-20
Multiple cross-site scripting (XSS) vulnerabilities in EMC Documentum WebTop before 6.7 SP1 P28 and 6.7 SP2 before P14 allow remote attackers to inject arbitrary web script or HTML via the (1) startat or (2) entryId parameter.

CVE-2014-2515
Published: 2014-08-20
EMC Documentum D2 3.1 before P24, 3.1SP1 before P02, 4.0 before P11, 4.1 before P16, and 4.2 before P05 does not properly restrict tickets provided by D2GetAdminTicketMethod and D2RefreshCacheMethod, which allows remote authenticated users to gain privileges via a request for a superuser ticket.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.