MVISION Insights: AvosLocker Ransomware Variant Abuses Driver File
Technical Articles ID:
KB95738
Last Modified: 6/9/2022
Last Modified: 6/9/2022
MVISION Insights: AvosLocker Ransomware Variant Abuses Driver File
Technical Articles ID:
KB95738
Last Modified: 6/9/2022 Environment
IMPORTANT: This Knowledge Base article discusses a specific threat that is being automatically tracked by MVISION Insights technology. The content is intended for use by MVISION Insights users, but is provided for general knowledge to all customers. Contact us for more information about MVISION Insights.
Summary
Description of Campaign A variant of the AvosLocker ransomware family was discovered disabling anti-virus solutions and detection evasion by using a legitimate Avast Anti-Rootkit Driver file. The malware also used an Nmap NSE script to scan endpoints vulnerable to the Log4shell Apache Log4j remote code execution vulnerability. The AvosLocker campaign also downloaded and used Netscan, Mimikatz, Impacket, PDQ, AnyDesk, and XenArmor to carry out the infection process. Our ATR Team gathers and analyzes information from multiple open and closed sources before disseminating intelligence reports. This campaign was researched by Trend Micro and shared publicly. How to use this article:
Minimum Content Versions Detection Summary Minimum set of Manual Rules to improve protection to block this campaign: IMPORTANT: Always follow best practices when you enable new rules and signatures. When you implement new rules or signatures, always set them to Report mode first and check the alerts generated. Resolve any issues that arise and then set the rules to Block. This step mitigates against triggering false positives and allows you to refine your configuration. For more information, see KB87843 - List of and best practices for Endpoint Security Dynamic Application Containment rules. Endpoint Security - Advanced Threat Protection: Rule ID: 4 Use GTI file reputation to identify trusted or malicious files
Host Intrusion Prevention: Rule ID: 6070 Hidden PowerShell Detected
Rule ID: 6083 PowerShell Command Restriction - NonInteractive Rule ID: 6081 PowerShell Command Restriction - NoProfile Rule ID: 6135 Unmanaged PowerShell Detected Rule ID: 6113 T1055 - Fileless Threat: Reflective Self Injection Endpoint Security - Access Protection Rules: Executing Mimikatz malware
Aggressive set of Manual Rules to improve protection to block this campaign: IMPORTANT: Always follow best practices when you enable new rules and signatures. When you implement new rules or signatures, always set them to Report mode first and check the alerts generated. Resolve any issues that arise and then set the rules to Block. This step mitigates against triggering false positives and allows you to refine your configuration. For more information, see KB87843 - List of and best practices for Endpoint Security Dynamic Application Containment rules. VirusScan Enterprise - Access Protection Rules: Prevent creation of new executable files in the Windows folder
Host Intrusion Prevention: Rule ID: 6010 Generic Application Hooking Protection
Rule ID: 6011 Generic Application Invocation Protection Rule ID: 1020 Windows Agent Shielding - File Access Rule ID: 1148 CMD Tool Access by a Network Aware Application Affected Products |
|