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

4/21/2017
10:52 AM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
100%
0%

Exploits Targeting Corporate Users Surged Nearly 30% In 2016

At same time, number of attacks targeting software vulnerabilities in systems used by consumers declined over 20%, Kaspersky Lab says in new report.

A new report from Kaspersky Lab this week holds some mixed news for individuals and organizations on a couple of fronts.

The report is based on an analysis of the threats detected and blocked worldwide by Kaspersky Lab’s antimalware products in 2016.

It showed that attacks against individual users decreased nearly 21% last year, from around 5.5 million users in 2015 to just over 4.3 million users in 2016.  

During the same period though, attacks against systems used by corporate users jumped sharply from around 540,000 in 2015 to 690,000 last year, representing a 28.4% increase in 12 months. For purposes of classification, Kaspersky Lab counted users of all systems protected by the company’s enterprise antimalware suite as corporate users.

Kaspersky Lab’s data revealed a similar dichotomy in exploit activity data. During 2016, several widely used exploit kits including Neutrino and Angler exited the underground scene and in the process significantly impacted the capabilities of many cybercrime groups to spread malware.

At the same time, and somewhat counter-intuitively, there were over 702 million attacks with exploits in 2016, a substantial 25% increase over 2015. What that meant was that though the number of individuals who encountered exploits decreased overall in 2016, the likelihood of their encountering an attack was actually higher.

“In other words, the number of websites infected with exploits and the number of spam messages with malicious attachments keeps growing,” the Kaspersky Lab report noted.

Alexander Liskin, a security expert at Kaspersky Lab says there are a couple of plausible reasons why corporate users ended up getting targeted more than consumers in 2016.

The slowdown in exploit kit activity, the proliferation of bug bounty programs and redoubled efforts by software vendors to address security bugs last year significantly increased the cost to cybercriminals of developing new exploits, Liskin says. So instead of targeting consumers, there appears to have been heightened interest in going after higher value corporate users.  

“Apparently, criminals consider these users valuable targets and are willing to invest into attacking them with exploits. This could be the reason for an increased amount of attacked corporate users,” Liskin says.

The trend is worrisome. The underground economy is driven by nearly the same principles as a legit one, he says. “Cybercriminals put efforts only into potentially profitable areas. If the number of corporate users attacked with exploits is growing, it means that it makes sense for bad guys to invest into exploits for such attacks.”

 

Stuxnet Flaw Still A Mark

Kaspersky Lab’s review of exploit activity in 2016 uncovered other important trends as well.

Exploits targeting Windows and browser vulnerabilities for instance dropped sharply by 21.56% and 33.4% respectively in 2016. But the number of users attacked with exploits targeting security flaws in Microsoft’s Office software surged by nearly 103%.

Similarly, attacks seeking to exploit vulnerabilities in Adobe Flash and Android jumped in 2016, but by relatively much smaller percentage. Adobe Flash exploits increased about 12% while Android exploits increased 23%.

Interestingly enough though, the vulnerability that was most targeted in 2016 was the Stuxnet LNK flaw that was exploited in the cyber attack on Iran’s nuclear enrichment facility in Natanz seven years ago. Though Microsoft first patched the issue back in 2010 and issued a more comprehensive patch for it in 2015, attackers have kept going at the flaw and have made it the most attacked vulnerability for the past several years in a row.

It’s hard to say exactly why that is happening, Liskin says. It is possible that many users are still using legacy systems with unpatched or pirated Windows versions. The fact that the LNK vulnerability gives malware authors a relatively easy way to make self-spreading malware could be another issue, he said.

“There are a lot of networks around the world that are unprotected and infected with LNK equipped malware endpoints,” Liskin said. “These endpoints pose a constant threat to other parts of the network and also generate lots of detections.”

The Stuxnet LNK flaw is not the only vulnerability that is being exploited in this manner. Another example is CVE-2012-0158 in Microsoft Office’s Active X control. That 2012 flaw, like Stuxnet LNK, continues to be widely exploited by ordinary cybercriminals and targeted attack actors because a lot of individuals and organizations are still running vulnerable versions of the software, Liskin said.

The key takeaway from the research is an old one. “Patch the software you have on your PC or corporate endpoints in time,” he says.” Even this single measure would significantly decrease the risk exploits pose to your private or corporate data.” 

Related stories:

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... 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-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.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...