Tag Archive for: Shatak

TrickBot teams up with Shatak phishers for Conti ransomware attacks


ransomware-lock

A threat actor tracked as Shatak (TA551) recently partnered with the ITG23 gang (aka TrickBot and Wizard Spider) to deploy Conti ransomware on targeted systems.

The Shatak operation partners with other malware developers to create phishing campaigns that download and infect victims with malware.

Researchers from IBM X-Force discovered that Shatak and TrickBot began working together in July 2021, with what appears to be good results, as the campaigns have continued until today.

A recent technical analysis from Cybereason provides more details on how the two distinct actors partnered to deliver ransomware attacks.

Attack starts with a phishing email

A typical infection chain starts with a phishing email sent by Shatak, carrying a password-protected archive containing a malicious document.

According to an October report by IBM X-Force, Shatak commonly uses reply-chain emails stolen from previous victims and adds password-protected archive attachments.

Example Shatak phishing email
Example Shatak phishing email
Source: IBM X-Force

These attachments contain scripts that execute base-64 encoded code to download and install the TrickBot or BazarBackdoor malware from a remote site.

The distribution sites used in the most recent campaign are based in European countries such as Germany, Slovakia, and the Netherlands.

Infection chain
Shatak’s infection chain
Source: Cybereason

After successfully deploying TrickBot and/or BazarBackdoor, ITG23 takes over by deploying a Cobalt Strike beacon on the compromised system, adding it to the scheduled tasks for persistence.

The Conti actors then use the dropped BazarBackdoor for network reconnaissance, enumerating users, domain admins, shared computers, and shared resources.

Then they steal user credentials, password hashes, and Active Directory data, and abuse what they can to spread laterally through the network.

Some signs of this activity include fiddling with registry values that enable the RDP connectivity and modifying Windows Firewall rules with the ‘netsh’ command.

Windows Defender’s real-time monitoring feature is also disabled to prevent alerts or interventions during the encryption process.

The next step is data exfiltration, which is the final stage before the file encryption,…

Source…