Thursday, March 13, 2025
HomeRansomwareHackers Rewritten The RansomExx Ransomware in Rust Language To Evade Detection

Hackers Rewritten The RansomExx Ransomware in Rust Language To Evade Detection

Published on

SIEM as a Service

Follow Us on Google News

There has recently been a discovery made by IBM Security X-Force Threat Researchers regarding a new variant of ransomware known as RansomExx that is dubbed RansomExx2 which was written in Rust language.

While threat actor behind this malware is known as Hive0091 (aka DefrayX). Apart from this, the RansomExx is also known by following these names:- 

  • Defray777
  • Ransom X

With the release of this new variant, a growing trend has been noticed in which ransomware developers are switching to the Rust programming language, which has become a common programming language for threat actors.

“If the Rust language continues to be adopted by malware developers, then this will eventually change as AV vendors will start increasing their abilities to detect it, so its advantages compared to other languages will lessen. At that point, we may see malware developers shift and experiment with different languages instead,”. IBM researchers said.

Technical Analysis

The primary reason for using Rust may have been its ability to offer lower detection rates for anti-virus programs. As a result of this growing trend, it is following the same patterns as strains such as:-

  • BlackCat
  • Hive
  • Luna

DefrayX (aka Hive0091) threat actor group is also known for the following strains:-

  • PyXie malware
  • Vatet loader
  • Defray ransomware

A wide variety of ransomware has previously been released by this group, including versions for Linux and Windows. That’s why there is a good possibility that the Windows version of the ransomware will also be released soon.

Though the new variant RansomExx2 has been molded in the Rust programming language, but it still maintains much of its functionality as its predecessor.

Several parameters will need to be passed to RansomExx2 as part of its command line arguments to encrypt the target directories. Following that, files are encrypted with AES-256, while the encryption keys are protected with RSA cryptography.

There has also been an update to the ransomware group’s website, where now the page title has been changed to:-

  • ransomexx2

When executed, ransomware enumerates and encrypts files in the directories specified by the user. With the exception of ransom notes and previously encrypted files, all files with a size of more than 40 bytes are encrypted.

A new file extension is given to every encrypted file so that it can be recognized easily. In every directory where the encrypted files are located, a ransom note will be dropped.

The ransom note is titled as “!_WHY_FILES_ARE_ENCRYPTED_!.txt” and this note contains the following information:-

There have been a number of victims of RansomExx’s operations since the operation was launched in 2018, including the following:

  • Government agencies
  • GIGABYTE
  • Zegna

There is a high probability that there will be more threats trying out Rust in the future, as determined by X-Force. Among the newest ransomware families to shift to Rust in 2022 is RansomExx.

“Like the Go programming language, which has experienced a similar surge in usage by threat actors over the past few years, Rust’s compilation process also results in more complex binaries that can be more time-consuming to analyze for reverse engineers.”

Managed DDoS Attack Protection for Applications – Download Free Guide

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Blind Eagle Targets Organizations with Weaponized .URL Files to Steal User Hashes

In a significant development in the cybersecurity landscape, APT-C-36, more commonly known as Blind...

INE Security Alert: Using AI-Driven Cybersecurity Training to Counter Emerging Threats

As Artificial Intelligence (AI)-powered cyber threats surge, INE Security, a global leader in cybersecurity...

Apache NiFi Vulnerability Exposes MongoDB Credentials to Attackers

A critical security vulnerability has been identified in Apache NiFi, a popular open-source data...

86,000+ Healthcare Staff Records Exposed Due to AWS S3 Misconfiguration

A non-password-protected database belonging to ESHYFT, a New Jersey-based HealthTech company, was recently discovered...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Medusa Ransomware Hits 300+ Critical Infrastructure Organizations Worldwide

The Federal Bureau of Investigation (FBI), Cybersecurity and Infrastructure Security Agency (CISA), and the...

Ebyte Ransomware Targets Windows Users with Advanced Encryption Techniques

A new ransomware variant, known as Ebyte Ransomware, has emerged as a significant threat...

Ragnar Loader Used by Multiple Ransomware Groups to Bypass Detection

Ragnar Loader, a sophisticated toolkit associated with the Ragnar Locker ransomware group, has been...