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.

Vulnerabilities / Threats

5/1/2018
05:15 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
100%
0%

Inside the Two Types of Account Takeover Attacks

There are two types of automated threats that leverage user credentials to target login pages with account takeover.

If your website has a login page, chances are good that it's targeted in account takeover attacks. Nearly all (96%) websites with login pages have bad bots and are hit with account takeover attempts, report researchers from the Distil Networks Research Lab.

Login pages are among the most abused Web pages, a finding from the 2017 Bad Bot report that prompted the research team to analyze the anatomy of account takeover attacks in greater depth. They studied data from 600 domains with login pages and pulled a smaller subset of 100 Web pages, which had the largest data sets of bad bot traffic, to study them further.

Account takeover attempts are intended to test credentials for validity. If they're legitimate, attackers sell the usernames and passwords on the Dark Web or gain account access to pilfer personal or financial information and sell that instead. Alternatively, they could use the account to transfer money, purchase goods or services, or spread disinformation campaigns.

There are two types of account takeover attempts and they occur at about the same frequency, researchers report. Half are volumetric, meaning the bot floods the login page with credentials in an attempt to verify them as soon as possible. These "credential-stuffing" attacks are easy to identify because they're accompanied by a spike in activity: the average credential stuffing attack will involve 35,000 to 50,000 requests and between 500% and 5,000% increase in login page traffic.

While they're easier for businesses to detect, volumetric attempts have the benefit of immediate gratification to perpetrators. "If you suddenly see a massive increase in failed logins, it's indicative of a volumetric attack," says Edward Roberts, Distil's director of product marketing. "If they can do that quickly and check with various sites across the Web, there's a benefit."

Volumetric attempts increase 300% after data breaches, when large amounts of credentials are made readily available to attackers. Bot operators assume two things: recently stolen credentials will still be active, and that people reuse their credentials across several websites. Researchers detected 17 volumetric credential stuffing attacks per day. The average number of attacks per organization is two to three per month; however, some sites are hit with as many as 10.

The other half of account takeover attempts are "low and slow," otherwise known as "credential cracking and stuffing" attacks. In these, bad bots consistently deliver login requests 24/7. They're slower-paced and because of that, it's tougher for businesses to pick up on them.

Volumetric attacks usually occur within a set time frame. Low and slow attempts rely on an ongoing stream of malicious requests. They have no distinct beginning or end.

Sites with login pages are likely to get hit, says Roberts, who notes airlines, e-commerce sites, and financial companies are often targeted. Attempts range from simple ones, which generate significant traffic per device, to sophisticated attacks with as few as two requests per device.

"In terms of the difference here, it's about how they are trying to hide themselves and how they're trying to be evasive," he explains. As they get more sophisticated, attackers make a greater effort to fly under organizations' radar.

Businesses can mitigate simple account takeover attempts by blocking IP addresses, IP organizations, or traffic from specific countries. Moderate attempts can be mitigated by blocking the device fingerprint. Sophisticated attacks are best addressed by using deep interrogation to verify the legitimacy of each request, researchers report.

Researchers noticed a few key trends in how attackers plan account takeover attempts. These attacks usually happen at a predetermined frequency; for example, sites hit with attacks on Wednesday will also experience their next attack on a Wednesday. Often, they conduct a "test round" to gauge the effectiveness of their bots ahead of a large attack. Attempts were also more likely to happen on Fridays and Saturdays, when most security teams are offline.

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Malicious USB Drive Hides Behind Gift Card Lure
Dark Reading Staff 3/27/2020
How Attackers Could Use Azure Apps to Sneak into Microsoft 365
Kelly Sheridan, Staff Editor, Dark Reading,  3/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: "I feel safe, but I can't understand a word he's saying."
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7599
PUBLISHED: 2020-03-30
All versions of com.gradle.plugin-publish before 0.11.0 are vulnerable to Insertion of Sensitive Information into Log File. When a plugin author publishes a Gradle plugin while running Gradle with the --info log level flag, the Gradle Logger logs an AWS pre-signed URL. If this build log is publicly ...
CVE-2020-7610
PUBLISHED: 2020-03-30
All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. The package will ignore an unknown value for an object's _bsotype, leading to cases where an object is serialized as a document rather than the intended BSON type.
CVE-2019-17560
PUBLISHED: 2020-03-30
The "Apache NetBeans" autoupdate system does not validate SSL certificates and hostnames for https based downloads. This allows an attacker to intercept downloads of autoupdates and modify the download, potentially injecting malicious code. “Apache NetBeans" version...
CVE-2019-17561
PUBLISHED: 2020-03-30
The "Apache NetBeans" autoupdate system does not fully validate code signatures. An attacker could modify the downloaded nbm and include additional code. "Apache NetBeans" versions up to and including 11.2 are affected by this vulnerability.
CVE-2020-8509
PUBLISHED: 2020-03-30
Zoho ManageEngine Desktop Central allows unauthenticated users to access PDFGenerationServlet, leading to sensitive information disclosure.