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.

Application Security //

Ransomware

1/22/2018
09:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

SamSam Ransomware Continues Making Hospitals Sick

SamSam or Samas continues to surface in hospitals and other healthcare facilities. The way the ransomware works shows how vulnerable healthcare is to these particular types of attacks.

SamSam, which also goes by the name Samas, has been an active bugger so far this year. The ransomware has been found at two Indiana hospitals -- one in Greenfield and another in Decatur.

Emphasizing how the threat actors are targeting healthcare in their focused attacks, the ransomware was also found to be present at a cloud-based electronic health records provider.

SamSam has been active since early 2016, when it used vulnerable JBoss application servers to gain a network foothold. Even then, the ransomware was not some widespread attack, but was singularly focused on healthcare targets.

From the beginning, the malware was never dependent on establishing communication with a command and control server, which is how most ransomware operates. It was self-sufficient in operation. It has also always demanded payment in Bitcoin.

By using vulnerable and accessible servers for its entry targets, it bypasses the need for enabling human action or any social engineering. The criminals in this effort have historically first surveyed the infiltrated network before unleashing their encryption, looking for the most valuable files that they can corrupt. This would increase their chances of having a bigger monetary payout when the malware is finally executed.

The current attacks use open Remote Desktop Protocol (RDP) connections to provide an entry point. While their usual technique is to force their way into an RDP connection with a brute-force dictionary attack, it has been reported that the criminals entered one hospital system by using an outside vendor's username and password.

How they obtained these legitimate credentials is unclear.

The affected hospital chose to pay the ransom, even though it had backups available. It seems to have been a business decision at its core, since doing the restore from backups would have cost more than the ransom.

Luckily for the hospital, the threat actors did send a decryption key that unlocked the encrypted records. Most authorities will advise not to pay a ransom in this situation, since a decrypting key may not be returned to the victim.

While SamSam is the symptom, the open RDP on the Internet is the root cause of the infection.

Each of these RDP endpoints has to be extremely validated from a necessary use standpoint before it gets deployed. It goes without saying that a strong password and two-factor authentication should be used on these kinds of connections, but the hospital attack showed that even valid credentials can provide an entry method.

The time has come for the healthcare sector to be cognizant of just how large a target that they are to these criminals. Perhaps then security will rise to the forefront of their operations before some patient's health is compromised.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/2/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9498
PUBLISHED: 2020-07-02
Apache Guacamole 1.1.0 and older may mishandle pointers involved inprocessing data received via RDP static virtual channels. If a userconnects to a malicious or compromised RDP server, a series ofspecially-crafted PDUs could result in memory corruption, possiblyallowing arbitrary code to be executed...
CVE-2020-3282
PUBLISHED: 2020-07-02
A vulnerability in the web-based management interface of Cisco Unified Communications Manager, Cisco Unified Communications Manager Session Management Edition, Cisco Unified Communications Manager IM & Presence Service, and Cisco Unity Connection could allow an unauthenticated, remote attack...
CVE-2020-5909
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, when users run the command displayed in NGINX Controller user interface (UI) to fetch the agent installer, the server TLS certificate is not verified.
CVE-2020-5910
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the Neural Autonomic Transport System (NATS) messaging services in use by the NGINX Controller do not require any form of authentication, so any successful connection would be authorized.
CVE-2020-5911
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the NGINX Controller installer starts the download of Kubernetes packages from an HTTP URL On Debian/Ubuntu system.