Vulnerabilities / Threats

1/7/2017
08:55 AM
Kelly Sheridan
Kelly Sheridan
Slideshows
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
100%
0%

What To Watch For With Ransomware: 2017 Edition

Ransomware will continue to evolve in 2017, bringing new and diverse threats to businesses. What changes are in store?
Previous
1 of 10
Next

(Image: Bacho via Shutterstock)

(Image: Bacho via Shutterstock)

Ransomware has businesses concerned - with good reason. Organizations across all industries are at risk of infection via email or Web attacks.

This brand of malware attack will grow and change in the new year. New variants, such as the new version of KillDisk that no longer just erases data but instead encrypts information and demands a Bitcoin ransom, are constantly surfacing.

Threat actors have successfully used ransomware to infiltrate businesses and demand money long before the rise in ransomware attacks in 2016. But ransomware is reaching a plateau now: stolen data is less valuable because of the sheer amount of it available on the black market, experts say. So attackers are getting more creative, generating new ways to broaden their reach and demand more money from their victims.

"Ransomware is a business, and as a business, it's going to evolve," says Allan Liska, intelligence analyst at Recorded Future.

Many security watchers believe ransomware will get worse. Some think attackers will take advantage of IoT devices and target consumers. Others think mobile devices are at greater risk.

What else is on the horizon for ransomware in 2017? We did some digging to find out. Read on to learn more about how threats will evolve, what to watch for, and how to mitigate risk.

 

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

Previous
1 of 10
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Valentine's Emails Laced with Gandcrab Ransomware
Kelly Sheridan, Staff Editor, Dark Reading,  2/14/2019
High Stress Levels Impacting CISOs Physically, Mentally
Jai Vijayan, Freelance writer,  2/14/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-20782
PUBLISHED: 2019-02-17
The GloBee plugin before 1.1.2 for WooCommerce mishandles IPN messages.
CVE-2019-8407
PUBLISHED: 2019-02-17
HongCMS 3.0.0 allows arbitrary file read and write operations via a ../ in the filename parameter to the admin/index.php/language/edit URI.
CVE-2019-8408
PUBLISHED: 2019-02-17
OneFileCMS 3.6.13 allows remote attackers to modify onefilecms.php by clicking the Copy button twice.
CVE-2016-10742
PUBLISHED: 2019-02-17
Zabbix before 2.2.21rc1, 3.x before 3.0.13rc1, 3.1.x and 3.2.x before 3.2.10rc1, and 3.3.x and 3.4.x before 3.4.4rc1 allows open redirect via the request parameter.
CVE-2019-8393
PUBLISHED: 2019-02-17
Hotels_Server through 2018-11-05 has SQL Injection via the API because the controller/api/login.php telephone parameter is mishandled.