AA22-152A: Karakurt Data Extortion Group

Cybersecurity
Original release date: June 1, 2022 | Last revised: June 2, 2022<br/><h3>Summary</h3><p class="tip-intro" style="font-size: 15px;"><em><b>Actions to take today to mitigate cyber threats from ransomware:</b></em><br />
• Prioritize patching known exploited vulnerabilities.<br />
• Train users to recognize and report phishing attempts.<br />
• Enforce multifactor authentication.</p>

<p>The Federal Bureau of Investigation (FBI), the Cybersecurity and Infrastructure Security Agency (CISA), the Department of the Treasury (Treasury), and the Financial Crimes Enforcement Network (FinCEN) are releasing this joint Cybersecurity Advisory (CSA) to provide information on the Karakurt data extortion group, also known as the Karakurt Team and Karakurt Lair. Karakurt actors have employed a variety of tactics, techniques, and procedures (TTPs), creating significant challenges for defense and mitigation. Karakurt victims have not reported encryption of compromised machines or files; rather, Karakurt actors have claimed to steal data and threatened to auction it off or release it to the public unless they receive payment of the demanded ransom. Known ransom demands have ranged from $25,000 to $13,000,000 in Bitcoin, with payment deadlines typically set to expire within a week of first contact with the victim.</p>

<p>Karakurt actors have typically provided screenshots or copies of stolen file directories as proof of stolen data. Karakurt actors have contacted victims’ employees, business partners, and clients [<a href="https://attack.mitre.org/versions/v11/techniques/T1591/002/">T1591.002</a>] with harassing emails and phone calls to pressure the victims to cooperate. The emails have contained examples of stolen data, such as social security numbers, payment accounts, private company emails, and sensitive business data belonging to employees or clients. Upon payment of ransoms, Karakurt actors have provided some form of proof of deletion of files and, occasionally, a brief statement explaining how the initial intrusion occurred.</p>

<p>Prior to January 5, 2022, Karakurt operated a leaks and auction website found at https://karakurt[.]group. The domain and IP address originally hosting the website went offline in the spring 2022. The website is no longer accessible on the open internet, but has been reported to be located elsewhere in the deep web and on the dark web. As of May 2022, the website contained several terabytes of data purported to belong to victims across North America and Europe, along with several “press releases” naming victims who had not paid or cooperated, and instructions for participating in victim data “auctions.”</p>

<p><a href="https://us-cert.cisa.gov/sites/default/files/publications/AA22-152A_Karakurt_Data_Extortion_Group.pdf">Download the PDF version of this report (pdf, 442kb)</a>.</p>

<p><a href="https://us-cert.cisa.gov/sites/default/files/publications/AA22-152A.stix.xml">Click here</a> for STIX.&nbsp;</p>
<h3>Technical Details</h3><h4>Initial Intrusion</h4>

<p>Karakurt does not appear to target any specific sectors, industries, or types of victims. During reconnaissance [<a href="https://attack.mitre.org/versions/v11/tactics/TA0043/">TA0043</a>], Karakurt actors appear to obtain access to victim devices primarily:</p>

<ul>
<li>By purchasing stolen login credentials [<a href="https://attack.mitre.org/versions/v11/techniques/T1589/001/">T1589.001</a>] [<a href="https://attack.mitre.org/versions/v11/techniques/T1589/002/">T1589.002</a>];&nbsp;</li>
<li>Via cooperating partners in the cybercrime community, who provide Karakurt access to already compromised victims; or&nbsp;</li>
<li>Through buying access to already compromised victims via third-party intrusion broker networks [<a href="https://attack.mitre.org/versions/v11/techniques/T1589/001/">T1589.001</a>].
<ul>
<li><strong>Note:</strong> Intrusion brokers, or intrusion broker networks, are malicious individual cyber actors or groups of actors who use a variety of tools and skills to obtain initial access to—and often create marketable persistence within—protected computer systems. Intrusion brokers then sell access to these compromised computer systems to other cybercriminal actors, such as those engaged in ransomware, business email compromise, corporate and government espionage, etc.&nbsp;</li>
</ul>
</li>
</ul>

<p>Common intrusion vulnerabilities exploited for initial access [<a href="https://attack.mitre.org/versions/v11/tactics/TA0001/">TA001</a>] in Karakurt events include the following:</p>

<ul>
<li>Outdated SonicWall SSL VPN appliances [<a href="https://attack.mitre.org/versions/v11/techniques/T1133/">T1133</a>] are vulnerable to multiple recent CVEs&nbsp;</li>
<li>Log4j “Log4Shell” Apache Logging Services vulnerability (CVE-2021-44228) [<a href="https://attack.mitre.org/versions/v11/techniques/T1190/">T1190</a>]</li>
<li>Phishing and spearphishing [<a href="https://attack.mitre.org/versions/v11/techniques/T1566/">T1566</a>]</li>
<li>Malicious macros within email attachments [<a href="https://attack.mitre.org/versions/v11/techniques/T1566/001/">T1566.001</a>]</li>
<li>Stolen virtual private network (VPN) or Remote Desktop Protocol (RDP) credentials [<a href="https://attack.mitre.org/versions/v11/techniques/T1078/">T1078</a>]</li>
<li>Outdated Fortinet FortiGate SSL VPN appliances <a href="https://attack.mitre.org/versions/v11/techniques/T1133/">[T1133</a>]/firewall appliances [<a href="https://attack.mitre.org/versions/v11/techniques/T1190/">T1190</a>] are vulnerable to multiple recent CVEs</li>
<li>Outdated and/or unserviceable Microsoft Windows Server instances</li>
</ul>

<h4>Network Reconnaissance, Enumeration, Persistence, and Exfiltration</h4>

<p>Upon developing or obtaining access to a compromised system, Karakurt actors deploy Cobalt Strike beacons to enumerate a network [<a href="https://attack.mitre.org/versions/v11/techniques/T1083/">T1083</a>], install Mimikatz to pull plain-text credentials [<a href="https://attack.mitre.org/versions/v11/techniques/T1078/">T1078</a>], use AnyDesk to obtain persistent remote control [<a href="https://attack.mitre.org/versions/v11/techniques/T1219/">T1219</a>], and utilize additional situation-dependent tools to elevate privileges and move laterally within a network.</p>

<p>Karakurt actors then compress (typically with 7zip) and exfiltrate large sums of data—and, in many cases, entire network-connected shared drives in volumes exceeding 1 terabyte (TB)—using open source applications and File Transfer Protocol (FTP) services [<a href="https://attack.mitre.org/versions/v11/techniques/T1048/">T1048</a>], such as Filezilla, and cloud storage services including rclone and Mega.nz [<a href="https://attack.mitre.org/versions/v11/techniques/T1567/002/">T1567.002</a>].&nbsp;</p>

<h4>Extortion</h4>

<p>Following the exfiltration of data, Karakurt actors present the victim with ransom notes by way of “readme.txt” files, via emails sent to victim employees over the compromised email networks, and emails sent to victim employees from external email accounts. The ransom notes reveal the victim has been hacked by the “Karakurt Team” and threaten public release or auction of the stolen data. The instructions include a link to a TOR URL with an access code. Visiting the URL and inputting the access code open a chat application over which victims can negotiate with Karakurt actors to have their data deleted.&nbsp;</p>

<p>Karakurt victims have reported extensive harassment campaigns by Karakurt actors in which employees, business partners, and clients receive numerous emails and phone calls warning the recipients to encourage the victims to negotiate with the actors to prevent the dissemination of victim data. These communications often included samples of stolen data—primarily personally identifiable information (PII), such as employment records, health records, and financial business records.</p>

<p>Victims who negotiate with Karakurt actors receive a “proof of life,” such as screenshots showing file trees of allegedly stolen data or, in some cases, actual copies of stolen files. Upon reaching an agreement on the price of the stolen data with the victims, Karakurt actors provided a Bitcoin address—usually a new, previously unused address—to which ransom payments could be made. Upon receiving the ransom, Karakurt actors provide some form of alleged proof of deletion of the stolen files, such as a screen recording of the files being deleted, a deletion log, or credentials for a victim to log into a storage server and delete the files themselves.</p>

<p>Although Karakurt’s primary extortion leverage is a promise to delete stolen data and keep the incident confidential, some victims reported Karakurt actors did not maintain the confidentiality of victim information after a ransom was paid. <strong>Note: </strong>the U.S. government strongly discourages the payment of any ransom to Karakurt threat actors, or any cyber criminals promising to delete stolen files in exchange for payments.</p>

<p>In some cases, Karakurt actors have conducted extortion against victims previously attacked by other ransomware variants. In such cases, Karakurt actors likely purchased or otherwise obtained previously stolen data. Karakurt actors have also targeted victims at the same time these victims were under attack by other ransomware actors. In such cases, victims received ransom notes from multiple ransomware variants simultaneously, suggesting Karakurt actors purchased access to a compromised system that was also sold to another ransomware actor.</p>

<p>Karakurt actors have also exaggerated the degree to which a victim had been compromised and the value of data stolen. For example, in some instances, Karakurt actors claimed to steal volumes of data far beyond the storage capacity of compromised systems or claimed to steal data that did not belong to the victim.<br />
&nbsp;</p>

<h3>Indicators of Compromise&nbsp;</h3>

<p>&nbsp;</p>

<table border="1" cellpadding="1" cellspacing="1" class="general-table" style="width: 600px; height: 312px; margin-left: auto; margin-right: auto;">
<thead>
<tr>
<th class="text-align-left" scope="col"><strong>Email</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td scope="col" style="text-align: left;">mark.hubert1986@gmail.com; karakurtlair@gmail.com; personal.information.reveal@gmail.com; ripidelfun1986@protonmail.com; gapreappballye1979@protonmail.com; confedicial.datas.download@protonmail.com; armada.mitchell94@protonmail.com</td>
</tr>
<tr>
<td scope="col" style="text-align: left;"><em>Protonmail email accounts in the following formats:</em><br />
victimname_treasure@protonmail.com<br />
victimname_jewels@protonmail.com<br />
victimname_files@protonmail.com</td>
</tr>
</tbody>
</table>

<p>&nbsp;</p>

<table border="1" cellpadding="1" cellspacing="1" class="general-table" style="width: 600px; height: 312px; margin-left: auto; margin-right: auto; ">
<thead>
<tr>
<th class="text-align-left" colspan="2" scope="col"><strong>Tools</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td scope="col" style="text-align: left;">Onion site</td>
<td scope="col" style="text-align: left;">https://omx5iqrdbsoitf3q4xexrqw5r5tfw7vp3vl3li3lfo7saabxazshnead.onion</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Tools</td>
<td scope="col" style="text-align: left;">Rclone.exe;; AnyDesk.exe; Mimikatz</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Ngrok</td>
<td scope="col" style="text-align: left;">SSH tunnel application SHA256 – 3e625e20d7f00b6d5121bb0a71cfa61f92d658bcd61af2cf5397e0ae28f4ba56</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">DLLs masquerading as legitimate Microsoft binaries to System32</td>
<td scope="col" style="text-align: left;">Mscxxx.dll: SHA1 – c33129a680e907e5f49bcbab4227c0b02e191770<br />
Msuxxx.dll: SHA1 – 030394b7a2642fe962a7705dcc832d2c08d006f5</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Msxsl.exe</td>
<td scope="col" style="text-align: left;">Legitimate Microsoft Command Line XSL Transformation Utility SHA1 – 8B516E7BE14172E49085C4234C9A53C6EB490A45</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">dllhosts.exe&nbsp;</td>
<td scope="col" style="text-align: left;">Rclone SHA1 – fdb92fac37232790839163a3cae5f37372db7235</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">rclone.conf</td>
<td scope="col" style="text-align: left;">Rclone configuration file</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">filter.txt</td>
<td scope="col" style="text-align: left;">Rclone file extension filter file</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">c.bat</td>
<td scope="col" style="text-align: left;">UNKNOWN</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">3.bat</td>
<td scope="col" style="text-align: left;">UNKNOWN</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Potential malicious document</td>
<td scope="col" style="text-align: left;">SHA1 – 0E50B289C99A35F4AD884B6A3FFB76DE4B6EBC14</td>
</tr>
</tbody>
</table>

<p>.</p>

<table border="1" cellpadding="1" cellspacing="1" class="general-table" style="width: 600px; height: 312px; margin-left: auto; margin-right: auto; ">
<thead>
<tr>
<th class="text-align-left" colspan="2" scope="col"><strong>Tools</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td scope="col" style="text-align: left;">Potential malicious document</td>
<td scope="col" style="text-align: left;">SHA1 – 7E654C02E75EC78E8307DBDF95E15529AAAB5DFF</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Malicious text file</td>
<td scope="col" style="text-align: left;">SHA1 – 4D7F4BB3A23EAB33A3A28473292D44C5965DDC95</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Malicious text file</td>
<td scope="col" style="text-align: left;">SHA1 – 10326C2B20D278080AA0CA563FC3E454A85BB32F</td>
</tr>
</tbody>
</table>

<p>&nbsp;</p>

<table border="1" cellpadding="1" cellspacing="1" class="general-table" style="width: 600px; height: 312px; margin-left: auto; margin-right: auto;">
<thead>
<tr>
<th class="text-align-left" scope="col"><strong>Cobalt Strike hashes</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td scope="col" style="text-align: left;">SHA256 – 563BC09180FD4BB601380659E922C3F7198306E0CAEBE99CD1D88CD2C3FD5C1B</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">SHA256 – 5E2B2EBF3D57EE58CADA875B8FBCE536EDCBBF59ACC439081635C88789C67ACA</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">SHA256 – 712733C12EA3B6B7A1BCC032CC02FD7EC9160F5129D9034BF9248B27EC057BD2</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">SHA256 – 563BC09180FD4BB601380659E922C3F7198306E0CAEBE99CD1D88CD2C3FD5C1B</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">SHA256 – 5E2B2EBF3D57EE58CADA875B8FBCE536EDCBBF59ACC439081635C88789C67ACA</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">SHA256 – 712733C12EA3B6B7A1BCC032CC02FD7EC9160F5129D9034BF9248B27EC057BD2</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">SHA1 – 86366bb7646dcd1a02700ed4be4272cbff5887af</td>
</tr>
</tbody>
</table>

<p>&nbsp;</p>

<table border="1" cellpadding="1" cellspacing="1" class="general-table" style="width: 600px; height: 312px; margin-left: auto; margin-right: auto; ">
<thead>
<tr>
<th class="text-align-left" colspan="2" scope="col"><strong>Ransom note text sample:</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td scope="col" style="text-align: left;">
<ol>
<li>&nbsp;</li>
</ol>
</td>
<td scope="col" style="text-align: left;">
<p>Here's the deal&nbsp;</p>

<p>We breached your internal network and took control over all of your systems.</p>
</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">
<p>&nbsp; &nbsp; &nbsp; 2.</p>
</td>
<td scope="col" style="text-align: left;">We analyzed and located each piece of more-or-less important files while spending weeks inside.</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">
<p>&nbsp; &nbsp; &nbsp; 3.&nbsp;</p>
</td>
<td scope="col" style="text-align: left;">We exfiltrated anything we wanted (xxx GB (including Private &amp; Confidential information, Intellectual Property, Customer Information and most important Your TRADE SECRETS)</td>
</tr>
</tbody>
</table>

<p>&nbsp;</p>

<table border="1" cellpadding="1" cellspacing="1" class="general-table" style="width: 600px; height: 312px; margin-left: auto; margin-right: auto; ">
<thead>
<tr>
<th class="text-align-left" colspan="2" scope="col"><strong>Ransom note text sample:</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td rowspan="2" scope="col" style="text-align: left;">
<p>FAQ:</p>
</td>
<td scope="col" style="text-align: left;">
<p>Who the hell are you?</p>
</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Who the hell are you?</td>
</tr>
</tbody>
</table>

<p>&nbsp;</p>

<table border="1" cellpadding="1" cellspacing="1" class="general-table" style="width: 600px; height: 312px; margin-left: auto; margin-right: auto;">
<thead>
<tr>
<th class="text-align-left" scope="col"><strong>Payment Wallets:</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td scope="col" style="text-align: left;">bc1qfp3ym02dx7m94td4rdaxy08cwyhdamefwqk9hp</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qw77uss7stz7y7kkzz7qz9gt7xk7tfet8k30xax</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1q8ff3lrudpdkuvm3ehq6e27nczm393q9f4ydlgt</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qenjstexazw07gugftfz76gh9r4zkhhvc9eeh47</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qxfqe0l04cy4qgjx55j4qkkm937yh8sutwhlp4c</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qw77uss7stz7y7kkzz7qz9gt7xk7tfet8k30xax</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qrtq27tn34pvxaxje4j33g3qzgte0hkwshtq7sq</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1q25km8usscsra6w2falmtt7wxyga8tnwd5s870g</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qta70dm5clfcxp4deqycxjf8l3h4uymzg7g6hn5</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qrkcjtdjccpy8t4hcna0v9asyktwyg2fgdmc9al</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1q3xgr4z53cdaeyn03luhen24xu556y5spvyspt8</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1q6s0k4l8q9wf3p9wrywf92czrxaf9uvscyqp0fu</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qj7aksdmgrnvf4hwjcm5336wg8pcmpegvhzfmhw</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qq427hlxpl7agmvffteflrnasxpu7wznjsu02nc</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qz9a0nyrqstqdlr64qu8jat03jx5smxfultwpm0</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qq9ryhutrprmehapvksmefcr97z2sk3kdycpqtr</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qa5v6amyey48dely2zq0g5c6se2keffvnjqm8ms</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qx9eu6k3yhtve9n6jtnagza8l2509y7uudwe9f6</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qtm6gs5p4nr0y5vugc93wr0vqf2a0q3sjyxw03w</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qta70dm5clfcxp4deqycxjf8l3h4uymzg7g6hn5</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qx9eu6k3yhtve9n6jtnagza8l2509y7uudwe9f6</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1qqp73up3xff6jz267n7vm22kd4p952y0mhcd9c8</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">bc1q3xgr4z53cdaeyn03luhen24xu556y5spvyspt8</td>
</tr>
</tbody>
</table>

<h3>Mitre&nbsp;Att&amp;ck Techniques</h3>

<p>Karakurt actors use the ATT&amp;CK techniques listed in table 1.<br />
&nbsp;</p>

<p class="text-align-center"><em>Table 1: Karakurt actors ATT&amp;CK techniques for enterprise</em></p>

<table align="center" border="1" cellpadding="1" cellspacing="1" class="general-table" style="width: 600px; height: 312px; margin-left: auto; margin-right: auto;">
<thead>
<tr>
<th colspan="3" scope="col"><u><strong>Reconnaissance</strong></u></th>
</tr>
</thead>
<tbody>
<tr>
<td class="text-align-center" scope="col">Technique Title</td>
<td class="text-align-center" scope="col" style="width: 75px;">ID</td>
<td class="text-align-center" scope="col" style="width: 345px;">Use</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Gather Victim Identify Information: Credentials</td>
<td scope="col" style="text-align: left; width: 75px;"><a href="https://attack.mitre.org/versions/v11/techniques/T1589/001/">T1589.001</a></td>
<td scope="col" style="text-align: left; width: 345px;">Karakurt actors have purchased stolen login credentials.</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Gather Victim Identity Information: Email Addresses</td>
<td scope="col" style="text-align: left; width: 75px;">
<p><a href="https://attack.mitre.org/versions/v11/techniques/T1589/002/">T1589.002</a></p>
</td>
<td scope="col" style="text-align: left; width: 345px;">Karakurt actors have purchased stolen login credentials including email addresses.</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Gather Victim Org Information: Business Relationships</td>
<td scope="col" style="text-align: left; width: 75px;"><a href="https://attack.mitre.org/techniques/T1591/002/">T1591.002</a></td>
<td scope="col" style="text-align: left; width: 345px;">Karakurt actors have leveraged victims' relationships with business partners.</td>
</tr>
<tr>
<td class="text-align-center" colspan="3" scope="col"><u><strong>Initial Access</strong></u></td>
</tr>
<tr>
<td class="text-align-center" scope="col">Technique Title</td>
<td class="text-align-center" scope="col" style="width: 75px;">ID</td>
<td class="text-align-center" scope="col" style="width: 345px;">Use</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Exploit Public-Facing Applications</td>
<td scope="col" style="text-align: left; width: 75px;"><a href="https://attack.mitre.org/versions/v11/techniques/T1190/">T1190</a></td>
<td scope="col" style="text-align: left; width: 345px;">Karakurt actors have exploited the Log4j "Log4Shell" Apache Logging Service vulnerability and vulnerabilities in outdated firewall appliances for gaining access to victims' networks.</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">External Remote Services</td>
<td scope="col" style="text-align: left; width: 75px;"><a href="https://attack.mitre.org/techniques/T1133/">T1133</a></td>
<td scope="col" style="text-align: left; width: 345px;">Karakurt actors have exploited vulnerabilities in outdated VPN appliances for gaining access to victims' networks.</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Phishing</td>
<td scope="col" style="text-align: left; width: 75px;"><a href="https://attack.mitre.org/techniques/T1566/">T1566</a></td>
<td scope="col" style="text-align: left; width: 345px;">Karakurt actors have used phishing and spearphishing to obtain access to victims' networks.</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Phishing – Spearphishing Attachment</td>
<td scope="col" style="text-align: left; width: 75px;"><a href="https://attack.mitre.org/versions/v11/techniques/T1566/001/">T1566.001</a></td>
<td scope="col" style="text-align: left; width: 345px;">Karakurt actors have sent malicious macros as email attachments to gain initial access.</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Valid Accounts</td>
<td scope="col" style="text-align: left; width: 75px;"><a href="https://attack.mitre.org/versions/v11/techniques/T1078/">T1078</a></td>
<td scope="col" style="text-align: left; width: 345px;">Karakurt actors have purchased stolen credentials, including VPN and RDP credentials, to gain access to victims' networks.</td>
</tr>
<tr>
<td class="text-align-center" colspan="3" scope="col"><u><strong>Privilege Escalation</strong></u></td>
</tr>
<tr>
<td class="text-align-center" scope="col">Technique Title</td>
<td class="text-align-center" scope="col" style="width: 75px;">ID</td>
<td class="text-align-center" scope="col" style="width: 345px;">Use</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Valid Accounts</td>
<td scope="col" style="text-align: left; width: 75px;"><a href="https://attack.mitre.org/versions/v11/techniques/T1078/">T1078</a></td>
<td scope="col" style="text-align: left; width: 345px;">Karakurt actors have installed Mimikatz to pull plain-text credentials.</td>
</tr>
<tr>
<td colspan="3" scope="col" style="text-align: left;">&nbsp;</td>
</tr>
<tr>
<td class="text-align-center" scope="col">Technique Title</td>
<td class="text-align-center" scope="col" style="width: 75px;">ID</td>
<td class="text-align-center" scope="col" style="width: 345px;">Use</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">File and Directory Discovery</td>
<td scope="col" style="text-align: left; width: 75px;"><a href="https://attack.mitre.org/versions/v11/techniques/T1083/">T1083</a></td>
<td scope="col" style="text-align: left; width: 345px;">Karakurt actors have deployed Cobalt Strike beacons to enumerate a network.</td>
</tr>
<tr>
<td colspan="3" scope="col" style="text-align: left;">&nbsp;</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Technique Title</td>
<td scope="col" style="text-align: left; width: 75px;">ID</td>
<td scope="col" style="text-align: left; width: 345px;">Use</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Remote Access Software</td>
<td scope="col" style="text-align: left; width: 75px;"><a href="https://attack.mitre.org/versions/v11/techniques/T1219/">T1219</a></td>
<td scope="col" style="text-align: left; width: 345px;">Karakurt actors have used AnyDesk to obtain persistent remote control of victims' systems.</td>
</tr>
<tr>
<td class="text-align-center" colspan="3" scope="col"><strong><u>Exfiltration&nbsp;</u></strong></td>
</tr>
<tr>
<td class="text-align-center" scope="col">Technique Title</td>
<td class="text-align-center" scope="col" style="width: 75px;">ID</td>
<td class="text-align-center" scope="col" style="width: 345px;">Use</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Exfiltration Over Alternative Protocol</td>
<td scope="col" style="text-align: left; width: 75px;"><a href="https://attack.mitre.org/versions/v11/techniques/T1048/">T1048</a></td>
<td scope="col" style="text-align: left; width: 345px;">Karakurt actors have used FTP services, including Filezilla, to exfiltrate data from victims' networks.</td>
</tr>
<tr>
<td scope="col" style="text-align: left;">Exfiltration Over Web Service: Exfiltration to Cloud Storage</td>
<td scope="col" style="text-align: left; width: 75px;"><a href="https://attack.mitre.org/versions/v11/techniques/T1567/002/">T1567.002</a></td>
<td scope="col" style="text-align: left; width: 345px;">Karakurt actors have used rclone and Mega.nz to exfiltrate data stolen from victims' networks.</td>
</tr>
</tbody>
</table>

<p>&nbsp;</p>
<h3>Mitigations</h3><ul>
<li>Implement a recovery plan to maintain and retain multiple copies of sensitive or proprietary data and servers in a physically separate, segmented, and secure location (i.e., hard drive, storage device, the cloud).</li>
<li>Implement network segmentation and maintain offline backups of data to ensure limited interruption to the organization.</li>
<li>Regularly back up data and password protect backup copies offline. Ensure copies of critical data are not accessible for modification or deletion from the system where the data resides.</li>
<li>Install and regularly update antivirus software on all hosts and enable real time detection.</li>
<li>Install updates/patch operating systems, software, and firmware as soon as updates/patches are released.</li>
<li>Review domain controllers, servers, workstations, and active directories for new or unrecognized accounts.&nbsp;</li>
<li>Audit user accounts with administrative privileges and configure access controls with least privilege in mind. Do not give all users administrative privileges.</li>
<li>Disable unused ports.</li>
<li>Consider adding an email banner to emails received from outside your organization.</li>
<li>Disable hyperlinks in received emails.</li>
<li>Enforce multi-factor authentication.&nbsp;</li>
<li>Use <a href="https://pages.nist.gov/800-63-3/">National Institute for Standards and Technology (NIST) standards</a> for developing and managing password policies.
<ul>
<li>Use longer passwords consisting of at least 8 characters and no more than 64 characters in length;</li>
<li>Store passwords in hashed format using industry-recognized password managers;</li>
<li>Add password user “salts” to shared login credentials;</li>
<li>Avoid reusing passwords;</li>
<li>Implement multiple failed login attempt account lockouts;</li>
<li>Disable password “hints”;</li>
<li>Refrain from requiring password changes more frequently than once per year.&nbsp;<strong>Note: </strong>NIST guidance suggests favoring longer passwords instead of requiring regular and frequent password resets. Frequent password resets are more likely to result in users developing password “patterns” cyber criminals can easily decipher.&nbsp;</li>
<li>Require administrator credentials to install software.</li>
</ul>
</li>
<li>Only use secure networks and avoid using public Wi-Fi networks. Consider installing and using a VPN.</li>
<li>Focus on cyber security awareness and training. Regularly provide users with training on information security principles and techniques as well as overall emerging cybersecurity risks and vulnerabilities (i.e., ransomware and phishing scams).</li>
</ul>

<h3>Resources</h3>

<ul>
<li>For additional resources related to the prevention and mitigation of ransomware, visit <a href="https://www.cisa.gov/stopransomware">Stopransomware.gov</a> as well as the <a href="https://www.cisa.gov/sites/default/files/publications/CISA_MS-ISAC_Ransomware Guide_S508C.pdf">CISA-Multi-State Information Sharing and Analysis Center (MS-ISAC) Joint Ransomware Guide</a> and NIST’s <a href="https://www.nccoe.nist.gov/projects/building-blocks/data-integrity/detect-respond">Data Integrity: Detecting and Responding to Ransomware and Other Destructive Events</a>. <a href="https://www.cisa.gov/stopransomware">Stopransomware.gov</a> is the U.S. government’s one-stop location for resources to tackle ransomware more effectively.</li>
<li>CISA’s <a href="https://github.com/cisagov/cset/releases/tag/v10.3.0.0">Ransomware Readiness Assessment</a> is a no-cost self-assessment based on a tiered set of practices to help organizations better assess how well they are equipped to defend and recover from a ransomware incident.&nbsp;</li>
<li>CISA offers a range of no-cost <a href="https://www.cisa.gov/cyber-hygiene-services">cyber hygiene services</a> to help critical infrastructure organizations assess, identify, and reduce their exposure to threats, including ransomware.&nbsp;</li>
<li>Financial Institutions must also ensure compliance with any applicable Bank Secrecy Act requirements, including suspicious activity reporting obligations. Indicators of Compromise, such as suspicious email addresses, file names, hashes, domains, and IP addresses, can be provided under Item 44 of the Suspicious Activity Report (SAR) form. For more information on mandatory and voluntary reporting of cyber events via suspicious activity reports (SARs), see FinCEN Advisory FIN-2016-A005, <em><a href="https://www.fincen.gov/resources/advisories/fincen-advisory-fin-2016-a005">Advisory to Financial Institutions on Cyber-Events and Cyber-Enabled Crime</a></em>, October 25, 2016, and FinCEN Advisory FIN-2021-A004, <em><a href="https://www.fincen.gov/resources/advisories/fincen-advisory-fin-2021-a004">Advisory on Ransomware and the Use of the Financial System to Facilitate Ransom Payments</a></em>, November 8, 2021, which updates FinCEN Advisory FIN-2020-A006.</li>
<li>The U.S. Department of State’s Rewards for Justice (RFJ) program offers a reward of up to $10 million for reports of foreign government malicious activity against U.S. critical infrastructure. See the <a href="https://www.state.gov/rewards-for-justice/">RFJ website</a> for more information and how to report information securely.&nbsp;</li>
</ul>
<h3>Revisions</h3>
<ul> <li>Initial Version: June 01, 2022</li> <li>June 2, 2022: Added STIX File</li> </ul>
<hr />
<div class="field field–name-body field–type-text-with-summary field–label-hidden field–item"><p class="privacy-and-terms">This product is provided subject to this <a href="https://us-cert.cisa.gov/privacy/notification">Notification</a> and this <a href="https://www.dhs.gov/privacy-policy">Privacy &amp; Use</a> policy.</p>
</div>

Scroll to Top