SoylentNews is people
SoylentNews
New NextCry Ransomware Encrypts Data on NextCloud Linux Servers
A new ransomware has been found in the wild that is currently undetected by antivirus engines on public scanning platforms. Its name is NextCry due to the extension appended to encrypted files and that it targets clients of the NextCloud file sync and share service.
The malware targets Nextcloud instances and for the time being there is no free decryption tool available for victims.
xact64, a Nextcloud user, posted on the BleepingComputer forum some details about the malware in an attempt to find a way to decrypt personal files.
Although his system was backed up, the synchronization process had started to update files on a laptop with their encrypted version on the server. He took action the moment he saw the files renamed but some of them still got processed by NextCry, otherwise known as Next-Cry.
“I realized immediately that my server got hacked and those files got encrypted. The first thing I did was pull the server to limit the damage that was being done (only 50% of my files got encrypted)” - xact64
Looking at the malware binary, Michael Gillespie said that the threat seems new and pointed out the NextCry ransomware uses Base64 to encode the file names. The odd part is that an encrypted file's content is also encoded this way, after first being encrypted.
The malware has not been submitted to the ID Ransomware service before but some details are available. BleepingComputer discovered that NextCry is a Python script compiled in a Linux ELF binary using pyInstaller. At the moment of writing, not one antivirus engine on the VirusTotal scanning platform detects it.
[...] Another Nexcloud user named Alex posted on the platform’s support page about being hit by NextCry ransomware. They say that access to their instance had been locked via SSH and ran the latest version of the software, suggesting that some vulnerability was exploited to get in.
In a conversation with BleepingComputer xact64 said that their Nextcloud installation runs on an old Linux computer with NGINX. This detail may provide the answer to how the attacker was able to get access.
“I have my own linux server (an old thin client I gave a second life) with nginx reverse-proxy” - xact64
On October 24, Nextcloud released an urgent alert about a remote code execution vulnerability that impacts the default Nextcloud NGINX configuration.
Tracked as CVE-2019-11043, the flaw is in the PHP-FPM (FastCGI Process Manager) component, included by some hosting providers like Nextcloud in their default setup. A public exploit exists and has been leveraged to compromised servers.
(Score: 0) by Anonymous Coward on Tuesday November 19 2019, @01:21AM (1 child)
For the experienced professional, it is indeed trivial.
Care to speculate on the outcome of winging it and performing surgery on your dog, vs taking him to the vet?
(Score: 2) by vux984 on Tuesday November 19 2019, @05:11PM
No, the experienced professionals know it it isn't trivial.
Backups aren't simply about making copies. It's also about verification, its about consistency and reliability. It's about performance. It's about encryption. It's often tied up with compliance (HIPAA etc -- the backups are just as covered as the originals and need to be appropriately controlled.) And lately its also VERY much about security. Anyone who thinks all that is trivial simply doesn't know what they are talking about. Hell, doing JUST the security part right is not trivial.