SETTRA Ransomware Deploys MeshAgent and gdrv.sys BYOVD Against Windows Systems

Huntress analysts have identified two separate incidents involving the newly observed SETTRA ransomware targeting Windows environments. The attacks combined the legitimate MeshAgent remote management tool with a Bring Your Own Vulnerable Driver technique using gdrv.sys to disable security controls. Victims included a consumer services and retail company hit in July and an industrial organization compromised in September. Initial access occurred through VPN connections or previously stolen credentials, after which operators deployed MeshAgent to maintain persistence and execute commands. Before encryption, the group deleted Windows event logs, disabled system recovery features, removed recovery partitions, and overwrote free disk space. Encrypted files received the .locked or .locked_wip extensions, with the ransomware binary named after the victim domain and ransom notes dropped as RESTORE_FILES.txt.

BoletimSecTranslated from Portuguese

Read at source

Huntress researchers have detailed two incidents involving a previously undocumented ransomware strain named SETTRA that targets Windows systems by combining a legitimate remote administration tool with a vulnerable driver.

The first victim, a consumer services and retail company, was compromised in July, while the second victim, an industrial organization, was hit in September. Initial access was obtained via VPN or previously stolen credentials, although the exact initial infection vector remains unconfirmed.

Once inside the network, operators deployed MeshAgent, a legitimate remote monitoring and management tool. This allowed them to maintain control, run commands, and move laterally while reducing reliance on custom malware that could trigger detections.

The second key component is the BYOVD technique. In the September incident, attackers loaded the vulnerable driver gdrv.sys to disable security services prior to encryption.

Before beginning the encryption process, the group took several steps to hinder recovery: Windows event logs were cleared, system recovery was disabled, recovery partitions were removed, and free disk space was overwritten.

Encrypted files were appended with the .locked extension in the first case and .locked_wip in the second. The ransomware executable itself was named after the victim’s domain, and ransom notes titled RESTORE_FILES.txt were placed in multiple directories.

Huntress recommends protecting VPN access with strong authentication, restricting remote management tools, maintaining tested offline backups, centralizing Windows log collection, and conducting simulated incident response exercises.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Ransomware & Extortion

Ransomware Group Emperador Claims 3.9 GB Data Theft from AB InBev
Russian Ransomware Groups INC and The Gentlemen Deploy AI-Driven Phantom Framework for Fully Automated Attacks
Creator of Ransomware Forum Ramp4u Hands Over 1.5 Billion Rubles to Russian Law Enforcement