Description of Campaign
Macaw Locker ransomware is most likely a variant of WastedLocker and linked to the Evil Corp/ Dridex Group. The ransomware was discovered in October 2021 and exfiltrates sensitive data before encrypting files.

McAfee Enterprise ATR is currently validating the found samples for overlap with Wastedlocker and other Dridex Group/Evil Corp related ransomware versions.
Until further notice, ATR has added MITRE techniques and rules for Wastedlocker to this Campaign and advises organisations to take similar precautions for Macaw Locker as they would do for other campaigns linked to the Dridex Group / Evil Corp.

How to use this article:

1. If a Threat Hunting table has been created, use the rules contained to search for malware related to this campaign. 
2. 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.
3. Scroll down and review the "Product Countermeasures" section of this article. Consider implementing them if they are not already in place.
4. Review KB91836 - Countermeasures for entry vector threats.
5. Review KB87843 - Dynamic Application Containment rules and best practices.
6. Review KB82925 - Identify what rule corresponds to an Adaptive Threat Protection and Threat Intelligence Exchange event.

Threat Hunting:

YARA

title: Suspicious Multiple File Rename Or Delete Occurred id: 97919310-06a7-482c-9639-92b67ed63cf8 status: experimental description: Detects multiple file rename or delete events occurrence within a specified period of time by a same user (these events may signalize about ransomware activity). tags: - attack.impact - attack.t1486 author: Vasiliy Burov, oscd.community date: 2020/10/16 references: - https://www.manageengine.com/data-security/how-to/how-to-detect-ransomware-attacks.html logsource: produc%WINDIR%\ service: security definition: 'Requirements: Audit Policy : Policies/Windows Settings/Security Settings/Local Policies/Audit Policy/Audit object access, Policies/Windows Settings/Security Settings/Advanced Audit Policy Configuration/Object Access' detection: selection: EventID: 4663 ObjectType: 'File' AccessList: '%%1537' Keywords: '0x8020000000000000' timeframe: 30s condition: selection | count() by SubjectLogonId > 10 falsepositives: - Software uninstallation - Files restore activities level: medium

This Knowledge Base article discusses a specific threat that is being tracked. The list of IOCs will change over time; check MVISION Insights for the latest IOCs.
 
Campaign IOC

Type	Value
SHA256	46878CF16C919445A9E5ADA3FF03CA3465C03323A3E8B31C2DE38EAE1C9259E4
SHA256	E3CC9AEFF3CA0B31FDA840C2AAEF6BE57DFF6DD7FDFB6072B13BD6116BACAE30

Minimum Content Versions:

Content Type	Version
V2 DAT (VirusScan Enterprise)	10162
V3 DAT (Endpoint Security)	4614

 
 
Detection Summary                               

IOC	Scanner	Detection
46878CF16C919445A9E5ADA3FF03CA3465C03323A3E8B31C2DE38EAE1C9259E4	AVEngine V2	GenericRXQO-PU!B9EE938BE159
	AVEngine V3	GenericRXQO-PU!B9EE938BE159
	JTI (ATP Rules)	JTI/Suspect.196612!b9ee938be159
	RP Static	-
	RP Dynamic	-

 

IOC	Scanner	Detection
E3CC9AEFF3CA0B31FDA840C2AAEF6BE57DFF6DD7FDFB6072B13BD6116BACAE30	AVEngine V2	Generic trojan.qy
	AVEngine V3	Generic trojan.qy
	JTI (ATP Rules)	JTI/Suspect.196612!92843c087ad5
	RP Static	-
	RP Dynamic	-

                                     
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:
Endpoint Security - Exploit Prevention:
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: