Vortex and Bugware Ransomware Use Open Source Tools to Target .NET Users
A pair of ransomware variants called Vortex and Bugware are encrypting victims’ files by using open source repositories and targeting .NET users, researchers warned. Based on an investigation published by Zscaler, those affected by the two families are being hit with demands that, in the case of Vortex, start at $100 and double within less than a week.
The researchers discovered live instances of the attacks using spam emails and links laden with malware. While Vortex was designed with open source encryption tool AESxWin, Bugware makes use of Hidden Tear code, a ransomware-like crypter sample.
A Vicious One-Two Ransomware Punch
According to SecurityWeek, the fraudsters behind Bugware masquerade as a Latin American utilities firm called GAS INFORMATICA LTDA. The ransomware displays a certificate that insists on a payment of 1,000 Brazilian real. Bugware also reinstates itself using a key whenever the victim logs on, stealing removable drives and other network files.
Vortex, meanwhile, uses a registry entry to stay active on a victim’s machine and even deletes backup versions of files the that victim may attempt to recover by reverting the system to a pre-infection state. Audio and video files are encrypted along with more traditional text files.
Although there are several differences between the two ransomware strains — Vortex is written in Polish while Bugware sends ransom messages in Portuguese, for example — SC Magazine reported that both use the Confuser packer and Microsoft Intermediate Language (MISL) for compilation purposes. Bugware also appears to have emerged just two months ago, while Vortex may have been active since March.
Forcing Victims to Pay Up
Both ransomware variants go to great lengths to minimize victims’ odds of retrieving their data without handing over money. As Virus Guides noted, files stolen by Vortex can only be decrypted if users know the password associated with AESxWin at the time of the attack. Bugware hides everything it can in a registry, including an RSA public key, AES key and even a base64-encoded key.
Taken together, these threats illustrate just how much damage cybercriminals with the right know-how can do with open source repositories.