Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

1/17/2017
02:20 PM
Connect Directly
Twitter
RSS
E-Mail
0%
100%

Credential-Stuffing Attacks Take Enterprise Systems By Storm

Automated credential-stuffing attempts makes up 90% of enterprise login traffic.

Billions of online credentials freshly stolen in 2016 are fueling a practice of automated login hacks that are overwhelming legitimate human-login traffic on enterprise Web properties.

A study out today from Shape Security shows that it's common for credential-stuffing login attempts to account for more than 90% of all login activity on Internet-facing systems at Fortune 100 firms.  

"In working with customers in retail, finance, travel, government, and other industries, Shape has seen millions of instances of credentials from reported breaches being used in credential stuffing attacks," the report says.

Online-credential breaches that don't expose any other personally identifiable information may seem like no big deal on the spectrum of massive security incidents. But the study out today shows that with automation, attackers are using stolen passwords quite effectively.

By using automated systems to stuff stolen credentials from one website into the login fields at another website, attackers can very quickly seek out instances where a user has recycled credentials at more than one website. If attackers have a large enough pool of stolen credentials to try across various other Web systems online, even a very slim success rate can yield them hundreds of thousands - or even millions - of accounts ripe for takeover.

Global organizations in 2016 reported more than 3 billion username and password combinations stolen, led first and foremost by Yahoo's massive 1.5 billion user breach. Shape Security researchers have found that by using those stolen login details, attackers utilizing automated credential stuffing tools on other websites can expect up to a 2% success rate for account takeover.

This means that for a breach of one million credentials on Website A, an attacker could set automation in motion against Website B and take over 20,000 accounts within hours. These attacks are typically repeated across Websites C-Z and so on, so that this single set of exposed credentials could help attackers gain access to hundreds of thousands of stolen accounts in very short order.

"Credential spills became a worldwide pandemic in 2016. While we have been observing credential spills and credential-stuffing attacks for many years, the scale of both in 2016 was remarkable," says Shuman Ghosemajumder, CTO for Shape. "The size and frequency of credential spills appears to be increasing, with the record for all-time largest credential spill being reset three times last year."

Shape reports that in its work with retail, finance, travel, government, and other industries in 2016, it observed millions of credentials exposed from reported breaches being used in credential- stuffing attacks. During one 4-month observation period at a major retailer, for example, Shape Security witnessed 15.5 million account login attempts. Scarily enough, 500,000 accounts at that retailer were on breached credential lists.

The difficulty with credential stuffing is that many companies don't have visibility into the volume of automated login traffic they're being hit with because these attacks aren't taking advantage of vulnerabilities per se. They're using the login functionality the way it is supposed to be used, simply scaling up the rate at which the credentials are plugged into the inputs. These attacks not only put users at risk, but they also put a traffic burden on infrastructure and could add to the login latency for real human users.

"A lot of public attention is focused on any organization that experiences a data breach and loses control of their users' passwords and personal information," Ghosemajumder says. "However, the real issue other companies should focus on is protecting themselves against those passwords being used to attack them and their own users.”

Related Content:

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27225
PUBLISHED: 2021-03-01
In Dataiku DSS before 8.0.6, insufficient access control in the Jupyter notebooks integration allows users (who have coding permissions) to read and overwrite notebooks in projects that they are not authorized to access.
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.