DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

PHOBOS ransomware infection at the Clinical Hospital No.1 CF Witting in Bucharest

Posted on July 24, 2021 by Dissent

The following is all machine translation of a notice from CERT-RO (Romania)

SRI, in cooperation with CERT-RO and the Clinical Hospital No.1 CF Witting in Bucharest, recently investigated a cyber attack with the ransomware application PHOBOS, which targeted the entity’s servers in the field of health.

Ransom Note
Credit: CERT-RO

Following the encryption of the data, the attackers requested the payment of a ransom for their decryption, a payment that was not made by the affected institution. However, the current activity of the hospital has not been interrupted, continuity being ensured through the use of offline registers.

Moreover, the present attack is similar to the one in the summer of 2019, when 4 other hospitals in Romania were affected by PHOBOS, in the context of the lack of antivirus solutions at the level of the IT&C infrastructure used by them. PHOBOS ransomware has a medium level of complexity, using as a method of infection, mainly Remote Desktop Protocol (RDP) connections.

Since the beginning of the pandemic in 2020, CERT-RO and cyber security experts from the Cyber ​​Volunteers 19 – Romania group have carried out joint warning and awareness campaigns dedicated to the medical units in the country. The main purpose of this initiative is to prevent, identify and properly address possible IT vulnerabilities of health care providers before it is too late.

The recommendations offered in this approach to support the medical environment are sometimes applied quickly and appropriately. But there are also cases where, for various reasons, the necessary security measures are not applied in time.

In order to prevent ransomware attacks, the experts of the CYBERINT and CERT-RO National Center recommend the rapid implementation of security policies and measures such as:

  • Using an updated antivirus solution;
  • Disable RDP service on all stations and servers in the network;
  • Update operating systems and all applications used;
  • Frequent change of passwords of all users, respecting the recommendations of complexity;
  • Periodic verification of all registered users, to identify new users, added illegally;
  • Backing up critical data on offline data carriers;
  • Keep encrypted data in the event that an decryption application may appear in the online environment.

h/t, @Metacurity

 


Related:

  • Some lower-tier ransomware gangs have formed a new RaaS alliance -- or have they?
  • Safaricom-Backed M-TIBA Victim of a Possible Data Breach Affecting Millions of Kenyans
  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
  • How a hacking gang held Italy’s political elites to ransom
  • Predatory Sparrow Strikes: Coordinated Cyberattacks Seek to Cripple Iran's Critical Infrastructure
  • On Reports of an Alleged Data Breach Involving G-Xchange, Inc. (GCash)
Category: Health DataMalwareNon-U.S.

Post navigation

← Mobile County Commission notifies employees of data breach; threat actors dump more data
Clubhouse denies data breach →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.