Trellix Insights: In-Depth Analysis of Raccoon Stealer V2
Technical Articles ID:
KB96158
Last Modified: 2022-11-15 12:28:16 Etc/GMT
Last Modified: 2022-11-15 12:28:16 Etc/GMT
Environment
IMPORTANT: This Knowledge Base article discusses a specific threat that is being automatically tracked by Trellix Insights technology. The content is intended for use by Trellix Insights users, but is provided for general knowledge to all customers. Contact us for more information about Trellix Insights.
Summary
Description of Campaign
After a brief break from operations, the Raccoon Stealer resumed operations with version 2 of the malware. The malware is sold and distributed through the threat actor's Telegram channel and advertised as a highly customizable stealer. Raccoon stealer targets users with fake installers and those seeking to obtain cracked software packages by repackaging the stealer with the cracked software versions. The malware analysis identifies methods used for C2 communication, target information collection, data staging, and data exfiltration.
Our Threat Research team gathers and analyzes information from multiple open and closed sources before disseminating intelligence reports. This campaign was researched by Sekoia and shared publicly.
How to use this article:
This Knowledge Base article discusses a specific threat that's being tracked. The list of IOCs will change over time; check Trellix Insights for the latest IOCs.
Campaign IOC
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: 239 Identify suspicious command parameter execution
Rule ID: 4 Use GTI file reputation to identify trusted or malicious files
Endpoint Security - Exploit Prevention:Rule ID: 6113 T1055 - Fileless Threat: Reflective Self Injection
Rule ID: 6086 PowerShell Command Restriction - Command
Rule ID: 6143 T1003 - Attempt to Dump Password Hash from SAM Database
Rule ID: 6135 Unmanaged PowerShell Detected
Rule ID: 6127 Suspicious LSASS Access from PowerShell
Rule ID: 8004 Fileless Threat: Malicious PowerShell Behavior Detected
Host Intrusion Prevention:Rule ID: 6081 PowerShell Command Restriction - NoProfile
Rule ID: 6113 T1055 - Fileless Threat: Reflective Self Injection
Rule ID: 6070 Hidden PowerShell Detected
Rule ID: 6083 PowerShell Command Restriction - NonInteractive
Rule ID: 6135 Unmanaged PowerShell Detected
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: 6053 Accessing other users home directory
Rule ID: 6010 Generic Application Hooking Protection
Rule ID: 1148 CMD Tool Access by a Network Aware Application
Rule ID: 6011 Generic Application Invocation Protection
Rule ID: 412 Double File Extension Execution
Rule ID: 1020 Windows Agent Shielding - File Access
Endpoint Security - Access Protection Rules:Creating new executable files in the Windows folder
After a brief break from operations, the Raccoon Stealer resumed operations with version 2 of the malware. The malware is sold and distributed through the threat actor's Telegram channel and advertised as a highly customizable stealer. Raccoon stealer targets users with fake installers and those seeking to obtain cracked software packages by repackaging the stealer with the cracked software versions. The malware analysis identifies methods used for C2 communication, target information collection, data staging, and data exfiltration.
Our Threat Research team gathers and analyzes information from multiple open and closed sources before disseminating intelligence reports. This campaign was researched by Sekoia and shared publicly.
How to use this article:
- If a Threat Hunting table has been created, use the rules contained to search for malware related to this campaign.
- Review the product detection table and confirm that your environment is at least on the specified content version.
To download the latest content versions, go to the Security Updates page. - Scroll down and review the "Product Countermeasures" section of this article. Consider implementing them if they are not already in place.
- Review
KB91836 - Countermeasures for entry vector threats . - Review KB87843 - Dynamic Application Containment rules and best practices.
- Review KB82925 - Identify what rule corresponds to an Adaptive Threat Protection and Threat Intelligence Exchange event.
meta: malware = "Raccoon" description = "Finds samples of the Raccoon Stealer V2 based on the RC4 decryption algorithm and the deobfuscation routine" author = "SEKOIA.IO" creation_date = "2022-06-16" modification_date = "2022-06-16" strings: $rc4_opcode = {99 f7 7d fc 8b 45 10 0f be 04 02 03 c1 03 f0 81 e6 ?? ?? ?? ?? 79 08 4e 81 ce ?? ?? ?? ?? 46} $deobfuscation = {8d 4d ?? 51 50 8b ce e8 ?? ?? 00 00 8d 55 ?? a3 ?? ?? ?? ?? b9 ?? ?? ?? ?? e8 ?? ?? ff ff 57} condition: $rc4_opcode and #deobfuscation > 20 and filesize < 70KB } |
This Knowledge Base article discusses a specific threat that's being tracked. The list of IOCs will change over time; check Trellix Insights for the latest IOCs.
Campaign IOC
Type | Value |
Minimum Content Versions
Content Type | Version |
Detection Summary
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
IOC | Scanner | Detection |
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
Endpoint Security - Exploit Prevention:
Rule ID: 6086 PowerShell Command Restriction - Command
Rule ID: 6143 T1003 - Attempt to Dump Password Hash from SAM Database
Rule ID: 6135 Unmanaged PowerShell Detected
Rule ID: 6127 Suspicious LSASS Access from PowerShell
Rule ID: 8004 Fileless Threat: Malicious PowerShell Behavior Detected
Host Intrusion Prevention:
Rule ID: 6113 T1055 - Fileless Threat: Reflective Self Injection
Rule ID: 6070 Hidden PowerShell Detected
Rule ID: 6083 PowerShell Command Restriction - NonInteractive
Rule ID: 6135 Unmanaged PowerShell Detected
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:
Host Intrusion Prevention:
Rule ID: 6010 Generic Application Hooking Protection
Rule ID: 1148 CMD Tool Access by a Network Aware Application
Rule ID: 6011 Generic Application Invocation Protection
Rule ID: 412 Double File Extension Execution
Rule ID: 1020 Windows Agent Shielding - File Access
Endpoint Security - Access Protection Rules: