Thursday, December 12, 2024
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

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.

- Advertisement - SIEM as a Service

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

GitLab Security Update, Patch for Critical Vulnerabilities

GitLab announced the release of critical security patches for its Community Edition (CE) and...

BadRAM Attack Breaches AMD Secure VMs with $10 Device

Researchers have uncovered a vulnerability that allows attackers to compromise AMD's Secure Encrypted Virtualization...

Splunk RCE Vulnerability Let Attackers Execute Remote Code

Splunk, the data analysis and monitoring platform, is grappling with a Remote Code Execution...

Europol Shutsdown 27 DDoS Service Provider Platforms

In a major international operation codenamed “PowerOFF,” Europol, collaborating with law enforcement agencies across...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

Reserachers Uncovered Zloader DNS Tunneling Tactics For Stealthy C2 Communication

Zloader, a sophisticated Trojan, has recently evolved with features that enhance its stealth and...

US Charged Chinese Hackers for Exploiting Thousands of Firewall

The US Treasury Department's Office of Foreign Assets Control (OFAC) has sanctioned Sichuan Silence...

Hackers Deploy Weaponized LNK Files for Malicious Payload Delivery

Researchers reported a phishing attack on December 4th, 2024, where malicious emails purportedly from...