AuditTeam Ransomware Exploits AV Drivers to Disable EDR

AuditTeam Ransomware Gang Poses as Security Auditors and Uses AV Drivers to Kill EDR Processes

AuditTeam, a newly identified ransomware operation, is deploying sophisticated social engineering by masquerading as legitimate security auditors. The threat actors send extortion demands disguised as professional audit reports, requesting “Audit & Consulting fees” instead of traditional ransom payments. Their technical arsenal includes exploiting signed antivirus driver vulnerabilities to terminate EDR processes through Bring Your Own Vulnerable Driver (BYOVD) attacks, allowing them to operate undetected in victim environments before deploying their encryption payload.

Introduction

The ransomware landscape continues evolving with threat actors adopting increasingly creative social engineering tactics alongside advanced evasion techniques. AuditTeam represents a dangerous convergence of psychological manipulation and technical sophistication that challenges traditional security assumptions.

By presenting ransom demands as legitimate security audit findings, AuditTeam exploits organizational trust in security processes. This approach may cause confusion among victims and delay incident response while organizations verify whether they’re dealing with actual auditors or attackers.

The group’s technical capabilities match their deceptive branding. Their use of vulnerable antivirus drivers to disable endpoint protection demonstrates advanced knowledge of Windows kernel-level operations and EDR architecture.

Background & Context

Ransomware operations have increasingly adopted distinct “brands” and operational personas to differentiate themselves in the crowded cybercrime marketplace. Some groups position themselves as corporate entities, while others embrace hacktivist narratives.

AuditTeam’s approach falls into a category of social engineering that leverages professional legitimacy. By framing extortion as audit findings, they tap into organizational familiarity with compliance processes, security assessments, and consultant engagements.

The BYOVD technique they employ has been used by several ransomware families including BlackCat/ALPHV, Cuba, and RobbinHood. This attack method exploits the trust Windows places in digitally signed drivers from legitimate vendors. Once loaded, these vulnerable drivers provide kernel-level access that EDR solutions cannot easily monitor or block.

Previous ransomware groups have used drivers like RTCore64.sys, DBUtil_2_3.sys, and gdrv.sys. These legitimate but vulnerable drivers become weapons when repurposed to terminate security processes.

Technical Breakdown

AuditTeam’s attack chain consists of multiple sophisticated stages that demonstrate careful planning and technical expertise.

Initial Access and Reconnaissance

While specific initial access vectors haven’t been fully documented, the group likely uses common entry points including phishing campaigns, exploiting perimeter vulnerabilities, or purchasing access from initial access brokers.

Once inside the environment, operators conduct extensive reconnaissance to identify critical systems, map network architecture, and locate high-value data for maximum leverage during negotiations.

EDR Evasion Through BYOVD

The critical technical innovation in AuditTeam’s approach is their EDR bypass mechanism:

  • Driver Deployment: Attackers drop a legitimate but vulnerable signed driver onto compromised systems
  • Service Creation: The vulnerable driver is registered as a Windows service
  • Kernel Access: The driver loads into kernel space with SYSTEM-level privileges
  • Process Termination: Through the vulnerable driver, attackers terminate EDR processes that would normally be protected

Example command structure for service creation:

sc create VulnDriver binPath= "C:\Windows\System32\drivers\vulnerable.sys" type= kernel
sc start VulnDriver

The vulnerable driver accepts commands from user-mode applications to terminate arbitrary processes, including protected security software.

Ransomware Deployment

With EDR disabled, AuditTeam deploys their encryption payload across the environment. The ransomware likely uses modern encryption algorithms such as ChaCha20 or AES combined with RSA for key protection.

File encryption proceeds rapidly without interference from endpoint protection, impacting file servers, databases, backups, and workstations.

Social Engineering Element

Post-encryption, victims receive ransom notes styled as professional security audit reports. These documents request payment for “Audit & Consulting fees” rather than explicitly demanding ransom, creating confusion about the nature of the incident.

This approach may cause victims to:

  • Question whether a legitimate audit occurred
  • Delay incident response while verifying legitimacy
  • Experience confusion in leadership about appropriate response
  • Hesitate to contact law enforcement

Impact & Risk Assessment

Technical Impact

Organizations compromised by AuditTeam face several severe consequences:

Data Encryption: Critical business systems become inaccessible, halting operations until recovery or ransom payment occurs.

EDR Blindness: The compromise of endpoint protection creates a dangerous visibility gap where additional malicious activity may occur undetected.

Lateral Movement Risk: With EDR disabled, attackers maintain persistent access for extended periods, potentially deploying additional malware or establishing alternative backdoors.

Recovery Complexity: Organizations must not only decrypt data but also rebuild trust in their security infrastructure after EDR compromise.

Business Impact

The disguise as legitimate auditors adds psychological and operational dimensions to the attack:

  • Delayed incident recognition extends dwell time
  • Confusion among non-technical leadership complicates decision-making
  • Potential compliance implications if audit requests are ignored
  • Reputational damage from sophisticated compromise

Risk Severity

AuditTeam should be considered a high-severity threat due to:

  • Advanced EDR evasion capabilities
  • Effective social engineering tactics
  • Demonstrated technical sophistication
  • Potential for extended undetected access

Vendor Response

Security vendors have begun responding to BYOVD threats broadly, though AuditTeam-specific signatures are still developing.

Microsoft has implemented driver blocklist policies that prevent known vulnerable drivers from loading. Organizations can enable this protection through Windows Defender Application Control (WDAC) or through registry-based driver blocklists.

EDR vendors including CrowdStrike, SentinelOne, Microsoft Defender for Endpoint, and Palo Alto Networks Cortex XDR have implemented behavioral detection for BYOVD attacks, monitoring for suspicious driver loading and process termination patterns.

Security researchers have published IOCs associated with commonly abused drivers, enabling organizations to proactively hunt for these artifacts in their environments.

Mitigations & Workarounds

Prevent Driver Exploitation

Implement Microsoft’s recommended driver block rules:

Set-RuleOption -FilePath "C:\WDAC\Policy.xml" -Option 0

Configure driver signature enforcement policies to restrict kernel driver loading to Microsoft-signed or organization-approved drivers only.

Network Segmentation

Implement strict network segmentation to limit lateral movement:

  • Separate critical infrastructure from general user networks
  • Implement jump servers for administrative access
  • Require multi-factor authentication for privileged access
  • Monitor east-west traffic for anomalous patterns

Email Security Controls

Since audit-themed communications may arrive via email:

  • Configure email filtering to quarantine unexpected audit-related communications
  • Implement sender verification for security consulting firms
  • Train users to verify audit requests through separate communication channels
  • Flag emails containing financial request language for review

Privileged Access Management

Restrict administrative privileges to prevent driver installation:

  • Implement least-privilege principles
  • Use PAM solutions to control administrative access
  • Monitor all driver installation events
  • Require approval workflows for system-level changes

Detection & Monitoring

EDR Process Monitoring

Monitor for unexpected termination of security processes:

Get-WinEvent -FilterHashtable @{LogName='System'; ID=7036} | 
Where-Object {$_.Message -match 'security|edr|antivirus'}

Alert on any EDR service stops, especially when not initiated through authorized management consoles.

Driver Loading Detection

Monitor Sysmon Event ID 6 (driver loaded) for suspicious drivers:


  
    RTCore64.sys
    DBUtil_2_3.sys
    gdrv.sys
  

Behavioral Analytics

Implement detection for suspicious patterns:

  • Multiple security processes terminating simultaneously
  • Driver loading followed by security service termination
  • Unusual service creation by non-administrative accounts
  • Unexpected kernel-mode operations from user applications

Audit Communication Verification

Establish procedures to verify unexpected audit notifications:

  • Maintain contacts for authorized auditing firms
  • Verify audit schedules through separate channels
  • Flag unsolicited audit communications for security review
  • Train finance teams to verify consulting fee requests

Best Practices

Implement Defense in Depth: No single security control prevents sophisticated attacks. Layer multiple defensive mechanisms including network segmentation, EDR, application control, and privileged access management.

Maintain Offline Backups: Store critical backups offline and air-gapped from production networks. Test restoration procedures regularly to ensure recovery capability without paying ransom.

Enable Kernel Protection: Utilize Windows security features including Hypervisor-Protected Code Integrity (HVCI), Secure Boot, and driver signature enforcement to prevent unauthorized kernel access.

Security Awareness Training: Educate staff about social engineering tactics including professional-appearing communications requesting payment. Establish verification procedures for unexpected financial requests.

Incident Response Planning: Develop and test incident response procedures specifically addressing ransomware scenarios. Include communication protocols, decision trees for ransom payment considerations, and recovery workflows.

Threat Hunting: Proactively search for compromise indicators rather than relying solely on automated detection. Hunt for vulnerable drivers, suspicious process terminations, and audit-themed communications.

Key Takeaways

  • AuditTeam ransomware disguises extortion as legitimate security audit findings, requesting “Audit & Consulting fees” to confuse victims and delay response
  • The group uses BYOVD techniques to load vulnerable signed antivirus drivers and terminate EDR processes, achieving kernel-level access and evading detection
  • Organizations should monitor for suspicious driver loading, unexpected EDR terminations, and unsolicited audit communications as compromise indicators
  • Implementing driver blocklists, network segmentation, and privileged access controls significantly reduces attack surface
  • Defense requires both technical controls against BYOVD attacks and organizational awareness of audit-themed social engineering tactics

References

  • Microsoft Security Blog: Vulnerable Driver Blocklist
  • MITRE ATT&CK T1068: Exploitation for Privilege Escalation
  • MITRE ATT&CK T1562.001: Impair Defenses – Disable or Modify Tools
  • LOLDrivers Project: Living Off The Land Drivers Documentation
  • CISA Alert: BYOVD Attacks and Mitigations

Stay updated at https://cydhaal.com — Your Daily Dose of Cyber Intelligence.
📧 Subscribe to our newsletter at https://cydhaal.com/newsletter/


Leave a Reply

Your email address will not be published. Required fields are marked *

💬 Join WhatsApp Channel 📲 Cydhaal App