Threat Intelligence

4/12/2016
08:00 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

How To Monetize Stolen Payment Card Data

The carding value chain not only relies on carders and buyers, but individuals who don't even know they're involved.

Bosses of the operations that turn stolen payment card data into cash have been known to take home as much as $1 million of profit in one year. One of the reasons they're so profitable: They scam and stiff thousands of the people who make the operation work.  

In a new report today, Hewlett Packard Enterprise Security Research outlined the process and the players in this value chain. To monetize stolen payment card data, organized criminals buy goods and then sell them for cash. According to HPE, in nearly all cases, card data was stolen from US accountholders, goods were bought in the US from online retailers in the US, and goods were shipped to Russia via intermediaries located in the US.

Beneath the bosses leading the operation are a network of administrators, "stuffers," and "drops," mostly managed via the Web. More specifically:  

  • Admins notify "stuffers" about what goods need to be purchased and, sometimes, what retailers they should be purchased from. Walmart, BestBuy, AT&T, Sprint, and Verizon were popular choices.
  • Stuffers, located in the US, buy goods online -- a wide variety of products ranging from electronics, to nutrition products, to toys, to rifle scopes. Stuffers are paid a 25- to 40% cut, depending upon the item.
  • The stuffers have the goods shipped to "drops," located in the US. 
  • Admins purchase labels from fraudulent shipping label services that forge labels for legitimate parcel delivery services like FedEx, UPS, and the US Postal Service.
  • Admins send the labels to drops.
  • Drops repackage goods with fraudulent labels and reship goods to Russia, using legitimate delivery services. The drops do not know that the items were bought illegally or that the shipping labels are fraudulent.

The drops were often "recruited" -- or, more accurately, scammed -- through social media advertising "work from home" opportunities that required no special skills but promised base salaries of as much as $2,500 per month.

However, the drops are almost never paid at all, according to the report. In fact, the admin's workflow software includes a system for tracking when drops sign up, quit, and become "dangerous" -- meaning they're expected to quit soon when they realize they are never going to see a dime for their reshipping efforts. Adding insult to injury, when drops sign up, they are convinced to submit a host of personal information -- including scans of government-issued IDs and proof of address -- as part of their "onboarding" process for the job.

From the report:

Recruiters find it more cost effective to recruit new drops from those looking for a "work from home" opportunity than to actually maintain and pay drops on an ongoing basis. This practice has the added benefit of isolating the most exposed part of the operation from the rest of the organization. Drops are exposed to very little if any of the true organization. ...

It's important to understand that drops are not a part of the organization; rather, they are as much a victim as others in the types of fraud schemes targeting human assets for exploitation.

Admins and stuffers, however, are key members of the organization. Admins manage the day-to-day technical functions of the Web interface through which business is conducted -- including taking orders for the products Russian buyers want, notifying stuffers about what those products are, connecting stuffers with drops, and tracking packages.

The operability and user interfaces of different re-shipper sites are so similar that researchers believe that these different operations must use the same software developers. 

     

Gain insight into the latest threats and emerging best practices for managing them. Attend the Security Track at Interop Las Vegas, May 2-6. Register now!

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
The Fundamental Flaw in Security Awareness Programs
Ira Winkler, CISSP, President, Secure Mentem,  7/19/2018
Number of Retailers Impacted by Breaches Doubles
Ericka Chickowski, Contributing Writer, Dark Reading,  7/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14492
PUBLISHED: 2018-07-21
Tenda AC7 through V15.03.06.44_CN, AC9 through V15.03.05.19(6318)_CN, and AC10 through V15.03.06.23_CN devices have a Stack-based Buffer Overflow via a long limitSpeed or limitSpeedup parameter to an unspecified /goform URI.
CVE-2018-3770
PUBLISHED: 2018-07-20
A path traversal exists in markdown-pdf version <9.0.0 that allows a user to insert a malicious html code that can result in reading the local files.
CVE-2018-3771
PUBLISHED: 2018-07-20
An XSS in statics-server <= 0.0.9 can be used via injected iframe in the filename when statics-server displays directory index in the browser.
CVE-2018-5065
PUBLISHED: 2018-07-20
Adobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have a Use-after-free vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the current user.
CVE-2018-5066
PUBLISHED: 2018-07-20
Adobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have an Out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.