Skip to main content
Mallory
← Back to News
ransomware-group-operationransomware-tooling-evolutioninitial-access-methodpersistence-method

MedusaLocker ransomware expands enterprise encryption and double-extortion operations

Threat Actor Intelligence · 6 sources · Updated 3mo ago · First seen Sep 29, 2025

MedusaLocker ransomware expands enterprise encryption and double-extortion operations

MedusaLocker has continued to evolve from its 2019 origins into a mature ransomware operation that targets enterprise networks through exposed or weakly secured RDP, stolen or brute-forced credentials, phishing, spam, and vulnerable VPN or edge devices. U.S. government reporting has described the threat as a ransomware-as-a-service model in which affiliates conduct intrusions and share proceeds with developers, while multiple technical profiles show the malware encrypting local disks, mapped drives, accessible SMB shares, and broader network resources after gaining a foothold. Later variants, including MedusaLocker v3 or BabyLockerKZ, also steal data to support double extortion and focus on maximizing damage inside victim environments rather than relying on external command-and-control traffic.

Across variants, MedusaLocker uses AES-256 encryption with RSA-2048 key protection, deletes shadow copies and backups to hinder recovery, and establishes persistence through scheduled tasks, roaming-profile executables, and registry-based mechanisms such as HKCU\SOFTWARE\PAIDMEMES or HKEY_CURRENT_USER\SOFTWARE\MDSLK\Self. Researchers and government agencies report additional behaviors including PowerShell execution, safe-mode reboots to impair defenses, UAC bypass, process termination to unlock files, ICMP network sweeping, CIDR-aware share discovery, hidden-volume mounting, and self-relaunch with a -network argument to widen encryption. The malware has used changing file extensions such as .meduza216 and varying ransom note names including How_to_back_files.html, HOW_TO_RECOVER_DATA, and related templates, with victims reported across healthcare, finance, government, and manufacturing.

Know this adversaryTTPs, infrastructure, and targeting history in one profile.
Get the profile
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

15 events · Oct 22, 2019 – Sep 29, 2025
  1. Sep 29, 20251y ago

    Howler Cell analyzed MedusaLocker v3 variant

    Howler Cell published an analysis of MedusaLocker v3, also called BabyLockerKZ, describing a newer variant with embedded XOR-decrypted configuration, registry-based persistence, subnet parsing, and expanded network encryption behavior.

    MedusaLocker v3 Ransomware Explained
  2. Mar 15, 20234y ago

    Cyble reported 24 MedusaLocker victims since January 2023

    Cyble reported that MedusaLocker had targeted 24 victims worldwide since January 2023, with the United States the most affected country and healthcare, education, and government among the targeted sectors. The report also analyzed a variant appending the .itlock4 extension and described its privilege escalation, persistence, backup deletion, and network/SMB enumeration behavior.

    Increase In MedusaLocker Ransomware Victims - Cyble
  3. Aug 11, 20224y ago

    U.S. agencies issued joint MedusaLocker advisory

    The FBI, CISA, the U.S. Department of the Treasury, and FinCEN issued a joint advisory describing MedusaLocker as a likely ransomware-as-a-service operation and detailing its tactics, techniques, and indicators of compromise.

    #StopRansomware: MedusaLocker | CISA
  4. May 2022

    MedusaLocker actors observed as recently as May 2022

    The joint U.S. government advisory stated that MedusaLocker actors had been observed as recently as May 2022.

    #StopRansomware: MedusaLocker | CISA
  5. Apr 23, 20207y ago

    Cisco Talos published MedusaLocker threat analysis

    Cisco Talos published a threat spotlight on MedusaLocker describing its network-aware encryption behavior, persistence via scheduled tasks, shadow copy deletion, and released Snort SIDs 53662 through 53665 for detection.

    Threat Spotlight: MedusaLocker
  6. Oct 22, 20197y ago

    BleepingComputer detailed early MedusaLocker behavior

    BleepingComputer published an early technical write-up on MedusaLocker describing its persistence via svchostt.exe and a scheduled task, shadow copy and backup deletion, mapped-drive access, and AES-plus-RSA encryption. The report also documented multiple extensions including .encrypted, .bomber, .boroff, .breakingbad, .locker16, .newlock, .nlocker, and .skynet, along with ransom notes HOW_TO_RECOVER_DATA.html or Readme.html using the contact emails sambolero@tutanoa.com and rightcheck@cock.li.

    MedusaLocker Ransomware Wants Its Share of Your Money
  7. Reported Oct 1, 201610y ago

    June 2020-era variant demanded 1 BTC

    A MedusaLocker variant from the 12 June 2020 timeframe used the .EG extension, demanded 1 BTC, and included the Bitcoin address 1BkmiGWPLum8MzusqZsq6Tn7v4oUjqPLjC.

    Шифровальщики-вымогатели The Digest "Crypto-Ransomware": MedusaLocker
  8. Reported Oct 1, 201610y ago

    Christmas 2019 variant introduced leak-extortion claim

    A separate MedusaLocker variant documented on 25 December 2019 used the .ReadInstructions extension and added a message claiming the victim network had been penetrated and confidential data stolen.

    Шифровальщики-вымогатели The Digest "Crypto-Ransomware": MedusaLocker
  9. Reported Oct 1, 201610y ago

    Christmas 2019 variant used RECOVER_INSTRUCTIONS note

    A MedusaLocker variant documented on 25 December 2019 used the .READINSTRUCTIONS extension and dropped the ransom note RECOVER_INSTRUCTIONS.html.

    Шифровальщики-вымогатели The Digest "Crypto-Ransomware": MedusaLocker
  10. Reported Oct 1, 201610y ago

    November variant used .ReadTheInstructions

    Variants documented in November 2019 used the .ReadTheInstructions extension and the ransom note INSTRUCTIONS.html.

    Шифровальщики-вымогатели The Digest "Crypto-Ransomware": MedusaLocker
  11. Reported Oct 1, 201610y ago

    Late-October variant switched to .decrypme

    Variants documented in late October 2019 used the .decrypme extension and dropped the ransom note HOW_TO_OPEN_FILES.html.

    Шифровальщики-вымогатели The Digest "Crypto-Ransomware": MedusaLocker
  12. Reported Oct 1, 201610y ago

    Variant using .encrypted extension documented

    A MedusaLocker variant documented on 22 October 2019 used the .encrypted extension and the contact emails crypt2020@outlook.com and cryptt2020@protonmail.com.

    Шифровальщики-вымогатели The Digest "Crypto-Ransomware": MedusaLocker
  13. Reported Oct 1, 201610y ago

    Sample timestamp recorded for MedusaLocker

    A cited MedusaLocker sample carried a file creation timestamp of 5 October 2019, providing an explicit anchor for early malware development or packaging.

    Шифровальщики-вымогатели The Digest "Crypto-Ransomware": MedusaLocker
  14. Reported Oct 1, 201610y ago

    MedusaLocker activity became notable

    MedusaLocker activity became notable in early October 2019 as the ransomware family began drawing broader attention from researchers.

    Шифровальщики-вымогатели The Digest "Crypto-Ransomware": MedusaLocker
  15. Reported Oct 1, 201610y ago

    Earliest MedusaLocker samples detected

    The earliest MedusaLocker samples referenced in the sources were detected in late September 2019, marking the beginning of observed activity for the ransomware family.

    Шифровальщики-вымогатели The Digest "Crypto-Ransomware": MedusaLocker
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Malware

1 linked

Observables

290 linked

Indicator values are masked on this page. View all 290 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See this adversary's TTPs, infrastructure, and targeting history, correlated against your exposure.
Get the Full Actor Profile
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.