Tuesday, March 4, 2025
HomeMalwareRobinhood Ransomware Borrow Vulnerable Driver To Kill Antivirus and Encrypt Windows System...

Robinhood Ransomware Borrow Vulnerable Driver To Kill Antivirus and Encrypt Windows System Files

Published on

SIEM as a Service

Follow Us on Google News

Researchers observed a new ransomware family called “Robinhood” that using a digitally signed vulnerable driver to bypass the protection by killing files belonging to endpoint security products, bypassing tamper protection and antivirus software to encrypt the system files.

Attackers using the Living off the Land technique for this ransomware attack to destructive file encryption portion and they are using Gigabyte driver vulnerability tracked as CVE-2018-19320.

Living off the land tactics is the use of operating system features or legitimate network administration tools or drivers to compromise victims’ networks.

During the attack, the Gigabyte driver used by them to load an unsigned driver into Windows to bypass the security protection and killing the security software process.

Researchers from Sophos said ” This is the first time we have observed ransomware shipping a trusted, signed (yet vulnerable) third party driver to patch the Windows kernel in-memory, load their own unsigned malicious driver, and take out security applications from kernel space”

Robinhood Bypass Windows Defenses

Researchers found that the Robinhood ransomware using various strategies to killing the endpoint security software process before starting its encryption process.

Samples of this ransomware reveal that the attackers using several files embedded in STEEL.EXE and is extracted to C:\WINDOWS\TEMP.

Following list of files that performing various operations during the infection.

STEEL.EXE – The Kill application that kills the processes and files of security products, using kernel drivers.

ROBNR.EXE – A driver installer that deploys both the benign, signed third-party driver and the criminals’ unsigned kernel driver.

GDRV.SYS – Vulnerable kernel driver, an outdated Authenticode-signed driver

RBNL.SYS – Malicious kernel driver that can kill processes and delete files from the kernel space.

These malicious drivers have various ways to delete files, but it doesn’t choose only one way to perform this task, instead, it runs them all sequentially, to ensure the file gets deleted.

Once its deleted the files,  STEEL.EXE kills all the processes associated with the files and displays the following ransomware notes.

Eventually, all the files in the compromised systems will be locked with strong encryption and demand the $10, 000 ransom in bitcoin.

Also, the ransomware notes displayed, the link will be provided to unlock the device by getting the private key, and they also warned not to contact the FBI and other security organizations.

Also Read: Ransomware Attack Response and Mitigation Checklist

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

Docusnap for Windows Flaw Exposes Sensitive Data to Attackers

A recently disclosed vulnerability in Docusnap's Windows client software (CVE-2025-26849) enables attackers to decrypt...

CISA Warns of Active Exploitation of Microsoft Windows Win32k Vulnerability

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added CVE-2018-8639, a decade-old Microsoft Windows...

Update Alert: Google Warns of Critical Android Vulnerabilities Under Exploit

Google’s March 2025 Android Security Bulletin has unveiled two critical vulnerabilities—CVE-2024-43093 and CVE-2024-50302—currently under...

BigAnt Server 0-Day Vulnerability Lets Attackers Run Malicious Code Remotely

A critical vulnerability in BigAntSoft's enterprise chat server software has exposed ~50 internet-facing systems...

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

Winos4.0 Malware Targets Windows Users Through Malicious PDF Files

A new wave of cyberattacks leveraging the Winos4.0 malware framework has targeted organizations in...

Lotus Blossom Hacker Group Uses Dropbox, Twitter, and Zimbra for C2 Communications

The Lotus Blossom hacker group, also known as Spring Dragon, Billbug, or Thrip, has...

Squidoor: Multi-Vector Malware Exploiting Outlook API, DNS & ICMP Tunneling for C2

A newly identified malware, dubbed "Squidoor," has emerged as a sophisticated threat targeting government,...