ブログ
/
Network
/
January 8, 2026

Under Medusa’s Gaze: How Darktrace Uncovers RMM Abuse in Ransomware Campaigns

Medusa ransomware increasingly exploits remote monitoring and management (RMM) tools for persistence, lateral movement, and data exfiltration. This blog explores Medusa’s tactics, real-world detections, and how anomaly-based solutions with Autonomous Response can stop attacks.
Inside the SOC
Darktrace cyber analysts are world-class experts in threat intelligence, threat hunting and incident response, and provide 24/7 SOC support to thousands of Darktrace customers around the globe. Inside the SOC is exclusively authored by these experts, providing analysis of cyber incidents and threat trends, based on real-world experience in the field.
Written by
Signe Zaharka
Principal Cyber Analyst
Default blog image
08
Jan 2026

What is Medusa Ransomware in 2025?

In 2025, the Medusa Ransomware-as-a-Service (RaaS) emerged as one of the top 10 most active ransomware threat actors [1]. Its growing impact prompted a joint advisory from the US Cybersecurity and Infrastructure Security Agency (CISA) and the Federal Bureau of Investigation (FBI) [3]. As of January 2026, more than 500 organizations have fallen victim to Medusa ransomware [2].

Darktrace previously investigated Medusa in a 2024 blog, but the group’s rapid expansion and new intelligence released in late 2025 has lead Darktrace’s Threat Research team to  investigate further. Recent findings include Microsoft’s research on Medusa actors exploiting a vulnerability in Fortra’s GoAnywhere MFT License Servlet (CVE-2025-10035)[4] and Zencec’s report on Medusa’s abuse of flaws in SimpleHelp’s remote support software (CVE-2024-57726, CVE-2024-57727, CVE-2024-57728) [5].

Reports vary on when Medusa first appeared in the wild. Some sources mention June 2021 as the earliest sightings, while others point to late 2022, when its developers transitioned to the RaaS model, as the true beginning of its operation [3][11].

Medusa Ransomware history and background

The group behind Medusa is known by several aliases, including Storm-1175 and Spearwing [4] [7]. Like its mythological namesake, Medusa has many “heads,” collaborating with initial access brokers (IABs) and, according to some evidence, affiliating with Big Game Hunting (BGH) groups such as Frozen Spider, as well as the cybercriminal group UNC7885 [3][6][13].

Use of Cyrillic in its scripts, activity on Russian-language cybercrime forums, slang unique to Russian criminal subcultures, and avoidance of targets in Commonwealth of Independent States (CIS) countries suggest that Medusa operates from Russia or an allied state [11][12].

Medusa ransomware should not be confused with other similarly named malware, such as the Medusa Android Banking Trojan, the Medusa Botnet/Medusa Stealer, or MedusaLocker ransomware. It is easily distinguishable from these variants because it appends the extension .MEDUSA to encrypted files and drops the ransom note !!!READ_ME_MEDUSA!!!.txt on compromised systems [8].

Who does Medusa Ransomware target?

The group appears to show little restraint, indiscriminately attacking organizations across all sectors, including healthcare, and is known to employ triple extortion tactics whereby sensitive data is encrypted, victims are threatened with data leaks, and additional pressure is applied through DDoS attacks or contacting the victim’s customers, rather than the more common double extortion model [13].

Medusa Ransomware TTPs

To attain initial access, Medusa actors typically purchase access to already compromised devices or accounts via IABs that employ phishing, credential stuffing, or brute-force attacks, and also target vulnerable or misconfigured Internet-facing systems.

In addition to the GoAnywhere MFT and SimpleHelp RMM flaws, other vulnerabilities exploited in Medusa attacks include ConnectWise ScreenConnect RMM (CVE-2024-1709), Microsoft Exchange Server (CVE-2021-34473, also known as ProxyShell), and Fortinet Enterprise Management Servers (CVE-2023-48788) [18][19][20][21][24][25].

Darktrace’s Coverage of Medusa Ransomware

Between December 2023 and November 2025, Darktrace observed multiple cases of file encryption related to Medusa ransomware across its customer base. When enabled, Darktrace’s Autonomous Response capability intervened early in the attack chain, blocking malicious activity before file encryption could begin.

Some of the affected were based in Europe, the Middle East and Africa (EMEA), others in the Americas (AMS), and the remainder in the Asia-Pacific and Japan region. The most impacted sectors were financial services and the automotive industry, followed by healthcare, and finally organizations in arts, entertainment and recreation, ICT, and manufacturing.

Remote Monitoring and Management (RMM) tool abuse

In most customer environments where Medusa file encryption attempts were observed, and in one case where the compromise was contained before encryption, unusual external HTTP connections associated with JWrapper were also detected. JWrapper is a legitimate tool designed to simplify the packaging, distribution, and management of Java applications, enabling the creation of executables that run across different operating systems. Many of the destination IP addresses involved in this activity were linked to SimpleHelp servers or associated with Atera.

Medusa actors appear to favor RMM tools such as SimpleHelp. Unpatched or misconfigured SimpleHelp RMM servers can serve as an initial access vector to the victims’ infrastructure.  After gaining access to SimpleHelp management servers, the threat actors edit server configuration files to redirect existing SimpleHelp RMM agents to communicate with unauthorized servers under their control.

The SimpleHelp tool is not only used for command-and-control (C2) and enabling persistence but is also observed during lateral movement within the network, downloading additional attack tools, data exfiltration, and even ransomware binary execution. Other legitimate remote access tools abused by Medusa in a similar manner to evade detection include Atera, AnyDesk, ScreenConnect, eHorus, N-able, PDQ Deploy/Inventory, Splashtop, TeamViewer, NinjaOne, Navicat, and MeshAgent [4][5][15][16][17].

Data exfiltration

Another correlation among Darktrace customers affected by Medusa was observed during the data exfiltration phase. In several environments, data was exfiltrated to the endpoints erp.ranasons[.]com or pruebas.pintacuario[.]mx (143.110.243[.]154, 144.217.181[.]205) over ports 443, 445, and 80. erp.ranasons[.]com was seemingly active between November 2024 and September 2025, while pruebas.pintacuario[.]mx was seen from November 2024 to March 2025. Evidence suggests that pruebas.pintacuario[.]mx previously hosted a SimpleHelp server [22][23].

Apart from RMM tools, Medusa is also known to use Rclone and Robocopy for data exfiltration [3][19]. During one Medusa compromise detected in mid-2024, the customer’s data was exfiltrated to external destinations associated with the Ngrok proxy service using an SSH-2.0-rclone client.

Medusa Compromise Leveraging SimpleHelp

In Q4 2025, Darktrace assisted a European company impacted by Medusa ransomware. The organization had partial Darktrace / NETWORK coverage and had configured Darktrace’s Autonomous Response capability to require manual confirmation for all actions. Despite these constraints, data received through the customer’s security integration with CrowdStrike Falcon enabled Darktrace analysts to reconstruct the attack chain, although the initial access vector remains unclear due to limited visibility.

In late September 2025, a device out of the scope of Darktrace's visibility began scanning the network and using RDP, NTLM/SMB, DCE_RPC, and PowerShell for lateral movement.

CrowdStrike “Defense Evasion: Disable or Modify Tools” alerts related to a suspicious driver (c:\windows\[0-9a-b]{4}.exe) and a PDQ Deploy executable (share=\\<device_hostname>\ADMIN$ file=AdminArsenal\PDQDeployRunner\service-1\exec\[0-9a-b]{4}.exe) suggest that the attackers used the Bring Your Own Vulnerable Driver (BYOVD) technique to terminate antivirus processes on network devices, leveraging tools such as KillAV or AbyssWorker along with the PDQ Software Deployment solution [19][26].

A few hours later, Darktrace observed the same device that had scanned the network writing Temp\[a-z]{2}.exe over SMB to another device on the same subnet. According to data from the CrowdStrike alert, this executable was linked to an RMM application located at C:\Users\<compromised_user>\Documents\[a-z]{2}.exe. The same compromised user account later triggered a CrowdStrike “Command and Control: Remote Access Tools” alert when accessing C:\ProgramData\JWrapper-Remote Access\JWrapper-Remote Access Bundle-[0-9]{11}\JWrapperTemp-[0-9]{10}-[0-9]{1}-app\bin\windowslauncher.exe [27].

An executable file associated with the SimpleHelp RMM tool being written to other devices using the SMB protocol, as detected by Darktrace.
Figure 1: An executable file associated with the SimpleHelp RMM tool being written to other devices using the SMB protocol, as detected by Darktrace.

Soon after, the destination device and multiple other network devices began establishing connections to 31.220.45[.]120 and 213.183.63[.]41, both of which hosted malicious SimpleHelp RMM servers. These C2 connections continued for more than 20 days after the initial compromise.

CrowdStrike integration alerts for the execution of robocopy . "c:\windows\\" /COPY:DT /E /XX /R:0 /W:0 /NP /XF RunFileCopy.cmd /IS /IT commands on several Windows servers, suggested that this utility was likely used to stage files in preparation for data exfiltration [19].

Around two hours later, Darktrace detected another device connecting to the attacker’s SimpleHelp RMM servers. This internal server had ‘doc’ in its hostname, indicating it was likely a file server. It was observed downloading documents from another internal server over SMB and uploading approximately 70 GiB of data to erp.ranasons[.]com (143.110.243[.]154:443).

Data uploaded to erp.ranasons[.]com and the number of model alerts from the exfiltrating device, represented by yellow and orange dots.
Figure 2: Data uploaded to erp.ranasons[.]com and the number of model alerts from the exfiltrating device, represented by yellow and orange dots.

Darktrace’s Cyber AI Analyst autonomously investigated the unusual connectivity, correlating the separate C2 and data exfiltration events into a single incident, providing greater visibility into the ongoing attack.

Cyber AI Analyst identified a file server making C2 connections to an attacker-controlled SimpleHelp server (213.183.63[.]41) and exfiltrating data to erp.ranasons[.]com.
Figure 3: Cyber AI Analyst identified a file server making C2 connections to an attacker-controlled SimpleHelp server (213.183.63[.]41) and exfiltrating data to erp.ranasons[.]com.
The same file server that connected to 213.183.63[.]41 and exfiltrated data to erp.ranasons[.]com was also observed attempting to connect to an IP address associated with Moscow, Russia (193.37.69[.]154:7070).
Figure 4: The same file server that connected to 213.183.63[.]41 and exfiltrated data to erp.ranasons[.]com was also observed attempting to connect to an IP address associated with Moscow, Russia (193.37.69[.]154:7070).

One of the devices connecting to the attacker's SimpleHelp RMM servers was also observed downloading 35 MiB from [0-9]{4}.filemail[.]com. Filemail, a legitimate file-sharing service, has reportedly been abused by Medusa actors to deliver additional malicious payloads [11].

A device controlled remotely via SimpleHelp downloading additional tooling from the Filemail file-sharing service.
Figure 5: A device controlled remotely via SimpleHelp downloading additional tooling from the Filemail file-sharing service.

Finally, integration alerts related to the ransomware binary, such as c:\windows\system32\gaze.exe and <device_hostname>\ADMIN$ file=AdminArsenal\PDQDeployRunner\service-1\exec\gaze.exe, along with “!!!READ_ME_MEDUSA!!!.txt” ransom notes were observed on network devices. This indicates that file encryption in this case was most likely carried out directly on the victim hosts rather than via the SMB protocol [3].

Conclusion

Threat actors, including nation-state actors and ransomware groups like Medusa, have long abused legitimate commercial RMM tools, typically used by system administrators for remote monitoring, software deployment, and device configuration, instead of relying on remote access trojans (RATs).

Attackers employ existing authorized RMM tools or install new remote administration software to enable persistence, lateral movement, data exfiltration, and ingress tool transfer. By mimicking legitimate administrative behavior, RMM abuse enables attackers to evade detection, as security software often implicitly trusts these tools, allowing attackers to bypass traditional security controls [28][29][30].

To mitigate such risks, organizations should promptly patch publicly exposed RMM servers and adopt anomaly-based detection solutions, like Darktrace / NETWORK, which can distinguish legitimate administrative activity from malicious behavior, applying rapid response measures through its Autonomous Response capability to stop attacks in their tracks.

Darktrace delivers comprehensive network visibility and Autonomous Response capabilities, enabling real-time detection of anomalous activity and rapid mitigation, even if an organization fall under Medusa’s gaze.

Credit to Signe Zaharka (Principal Cyber Analyst) and Emma Foulger (Global Threat Research Operations Lead

Edited by Ryan Traill (Analyst Content Lead)

Appendices

List of Indicators of Compromise (IoCs)

IoC - Type - Description + Confidence + Time Observed

185.108.129[.]62 IP address Malicious SimpleHelp server observed during Medusa attacks (High confidence) - March 7, 2023

185.126.238[.]119 IP address Malicious SimpleHelp server observed during Medusa attacks (High confidence) - November 26-27, 2024

213.183.63[.]41 IP address Malicious SimpleHelp server observed during Medusa attacks (High confidence) - November 28, 2024 - Sep 30, 2025

213.183.63[.]42 IP address Malicious SimpleHelp server observed during Medusa attacks (High confidence) - July 4 -9 , 2024

31.220.45[.]120 IP address Malicious SimpleHelp server observed during Medusa attacks (High confidence) - September 12 - Oct 20 , 2025

91.92.246[.]110 IP address Malicious SimpleHelp server observed during Medusa attacks (High confidence) - May 24, 2024

45.9.149[.]112:15330 IP address Malicious SimpleHelp server observed during Medusa attacks (High confidence) - June 21, 2024

89.36.161[.]12 IP address Malicious SimpleHelp server observed during Medusa attacks (High confidence) - June 26-28, 2024

193.37.69[.]154:7070 IP address Suspicious RU IP seen on a device being controlled via SimpleHelp and exfiltrating data to a Medusa related endpoint - September 30 - October 20, 2025

erp.ranasons[.]com·143.110.243[.]154 Hostname Data exfiltration destination - November 27, 2024 - September 30, 2025

pruebas.pintacuario[.]mx·144.217.181[.]205 - Hostname Data exfiltration destination - November 27, 2024  -  March 26, 2025

lirdel[.]com · 44.235.83[.]125/a.msi (1b9869a2e862f1e6a59f5d88398463d3962abe51e19a59) File & hash Atera related file downloaded with PowerShell - June 20, 2024

wizarr.manate[.]ch/108.215.180[.]161:8585/$/1dIL5 File Suspicious file observed on one of the devices exhibiting unusual activity during a Medusa compromise - February 28, 2024

!!!READ_ME_MEDUSA!!!.txt" File - Ransom note

*.MEDUSA - File extension        File extension added to encrypted files

gaze.exe – File - Ransomware binary

Darktrace Model Coverage

Darktrace / NETWORK model detections triggered during connections to attacker controlled SimpleHelp servers:

Anomalous Connection/Anomalous SSL without SNI to New External

Anomalous Connection/Multiple Connections to New External UDP Port

Anomalous Connection/New User Agent to IP Without Hostname

Anomalous Connection/Rare External SSL Self-Signed

Anomalous Connection/Suspicious Self-Signed SSL

Anomalous File/EXE from Rare External Location

Anomalous Server Activity/Anomalous External Activity from Critical Network Device

Anomalous Server Activity/New User Agent from Internet Facing System

Anomalous Server Activity/Outgoing from Server

Anomalous Server Activity/Rare External from Server

Compromise/High Volume of Connections with Beacon Score

Compromise/Large Number of Suspicious Failed Connections

Compromise/Ransomware/High Risk File and Unusual SMB

Device/New User Agent

Unusual Activity/Unusual External Data to New Endpoint

Unusual Activity/Unusual External Data Transfer

Darktrace / NETWORK Model Detections during the September/October 2025 Medusa attack:

Anomalous Connection / Data Sent to Rare Domain

Anomalous Connection / Download and Upload

Anomalous Connection / Low and Slow Exfiltration

Anomalous Connection / New User Agent to IP Without Hostname

Anomalous Connection / Uncommon 1 GiB Outbound

Anomalous Connection / Unusual Admin RDP Session

Anomalous Connection / Unusual Incoming Long Remote Desktop Session

Anomalous Connection / Unusual Long SSH Session

Anomalous File / EXE from Rare External Location

Anomalous File / Internal/Unusual Internal EXE File Transfer

Anomalous Server Activity / Anomalous External Activity from Critical Network Device

Anomalous Server Activity / Outgoing from Server

Anomalous Server Activity / Rare External from Server

Compliance / Default Credential Usage

Compliance / High Priority Compliance Model Alert

Compliance / Outgoing NTLM Request from DC

Compliance / Possible Unencrypted Password File On Server

Compliance / Remote Management Tool On Server

Compromise / Large Number of Suspicious Failed Connections

Compromise / Large Number of Suspicious Successful Connections

Compromise / Ransomware/High Risk File and Unusual SMB

Compromise / Suspicious Beaconing Behaviour

Compromise / Suspicious HTTP and Anomalous Activity

Compromise / Sustained SSL or HTTP Increase

Compromise / Sustained TCP Beaconing Activity To Rare Endpoint

Device / ICMP Address Scan

Device / Increase in New RPC Services

Device / Initial Attack Chain Activity

Device / Large Number of Model Alert

Device / Large Number of Model Alerts from Critical Network Device

Device / Lateral Movement and C2 Activity

Device / Multiple C2 Model Alert

Device / Network Scan

Device / Possible SMB/NTLM Reconnaissance

Device / Spike in LDAP Activity

Device / Suspicious Network Scan Activity

Device / Suspicious SMB Scanning Activity

Security Integration / High Severity Integration Incident

Security Integration / Low Severity Integration Incident

Unusual Activity / Enhanced Unusual External Data Transfer

Unusual Activity / Internal Data Transfer

Unusual Activity / Unusual External Activity

Unusual Activity / Unusual External Data to New Endpoint

Unusual Activity / Unusual External Data Transfer

User / New Admin Credentials on Server

Autonomous Response Actions

Antigena / Network/External Threat/Antigena File then New Outbound Block

Antigena / Network/External Threat/Antigena Ransomware Block

Antigena / Network/External Threat/Antigena Suspicious Activity Block

Antigena / Network/External Threat/Antigena Suspicious File Block

Antigena / Network/Insider Threat/Antigena Internal Anomalous File Activity

Antigena / Network/Insider Threat/Antigena Internal Data Transfer Block

Antigena / Network/Insider Threat/Antigena Large Data Volume Outbound Block

Antigena / Network/Insider Threat/Antigena Network Scan Block

Antigena / Network/Insider Threat/Antigena Unusual Privileged User Activities Block

Antigena / Network/Significant Anomaly/Antigena Alerts Over Time Block

Antigena / Network/Significant Anomaly/Antigena Controlled and Model Alert

Antigena / Network/Significant Anomaly/Antigena Enhanced Monitoring from Server Block

Antigena / Network/Significant Anomaly/Antigena Significant Server Anomaly Block

Antigena / Network/Significant Anomaly/Repeated Antigena Alerts

MITRE ATT&CK Mapping

Technique Name, Tactic, ID, Sub-Technique

Application Layer Protocol , COMMAND AND CONTROL , T1071

Automated Collection , COLLECTION , T1119

Automated Exfiltration , EXFILTRATION , T1020

Brute Force , CREDENTIAL ACCESS , T1110

Client Configurations , RECONNAISSANCE , T1592.004 , T1592

Cloud Accounts , DEFENSE EVASION ,  PERSISTENCE ,  PRIVILEGE ESCALATION ,  INITIAL ACCESS , T1078.004 , T1078

Command-Line Interface , EXECUTION ICS , T0807

Credential Stuffing , CREDENTIAL ACCESS , T1110.004 , T1110

Data Encrypted for Impact , IMPACT , T1486

Data from Network Shared Drive , COLLECTION , T1039

Data Obfuscation , COMMAND AND CONTROL , T1001

Data Staged , COLLECTION , T1074

Data Transfer Size Limits , EXFILTRATION , T1030

Default Accounts , DEFENSE EVASION ,  PERSISTENCE ,  PRIVILEGE ESCALATION ,  INITIAL ACCESS , T1078.001 , T1078

Default Credentials , LATERAL MOVEMENT ICS , T0812

Distributed Component Object Model , LATERAL MOVEMENT , T1021.003 , T1021

Drive-by Compromise , INITIAL ACCESS ICS , T0817

Drive-by Compromise , INITIAL ACCESS , T1189

Email Collection , COLLECTION , T1114

Exfiltration Over Alternative Protocol , EXFILTRATION , T1048

Exfiltration Over C2 Channel , EXFILTRATION , T1041

Exfiltration to Cloud Storage , EXFILTRATION , T1567.002 , T1567

Exploit Public-Facing Application , INITIAL ACCESS , T1190

Exploitation for Privilege Escalation , PRIVILEGE ESCALATION , T0890

Exploitation of Remote Services , LATERAL MOVEMENT , T1210

Exploits , RESOURCE DEVELOPMENT , T1588.005 , T1588

File and Directory Discovery , DISCOVERY , T1083

File Deletion , DEFENSE EVASION , T1070.004 , T1070

Graphical User Interface , EXECUTION ICS , T0823

Ingress Tool Transfer , COMMAND AND CONTROL , T1105

Lateral Tool Transfer , LATERAL MOVEMENT , T1570

LLMNR/NBT-NS Poisoning and SMB Relay , CREDENTIAL ACCESS ,  COLLECTION , T1557.001 , T1557

Malware , RESOURCE DEVELOPMENT , T1588.001 , T1588

Network Service Scanning , DISCOVERY , T1046

Network Share Discovery , DISCOVERY , T1135

Non-Application Layer Protocol , COMMAND AND CONTROL , T1095

Non-Standard Port , COMMAND AND CONTROL , T1571

One-Way Communication , COMMAND AND CONTROL , T1102.003 , T1102

Pass the Hash , DEFENSE EVASION ,  LATERAL MOVEMENT , T1550.002 , T1550

Password Cracking , CREDENTIAL ACCESS , T1110.002 , T1110

Password Guessing , CREDENTIAL ACCESS , T1110.001 , T1110

Password Spraying , CREDENTIAL ACCESS , T1110.003 , T1110

Program Download , LATERAL MOVEMENT ICS , T0843

Program Upload , COLLECTION ICS , T0845

Remote Access Software , COMMAND AND CONTROL , T1219

Remote Desktop Protocol , LATERAL MOVEMENT , T1021.001 , T1021

Remote System Discovery , DISCOVERY , T1018

Scanning IP Blocks , RECONNAISSANCE , T1595.001 , T1595

Scheduled Transfer , EXFILTRATION , T1029

Spearphishing Attachment , INITIAL ACCESS ICS , T0865

Standard Application Layer Protocol , COMMAND AND CONTROL ICS , T0869

Supply Chain Compromise , INITIAL ACCESS ICS , T0862

User Execution , EXECUTION ICS , T0863

Valid Accounts , DEFENSE EVASION ,  PERSISTENCE ,  PRIVILEGE ESCALATION ,  INITIAL ACCESS , T1078

Valid Accounts , PERSISTENCE ICS ,  LATERAL MOVEMENT ICS , T0859

Vulnerabilities , RESOURCE DEVELOPMENT , T1588.006 , T1588

Vulnerability Scanning , RECONNAISSANCE , T1595.002 , T1595

Web Protocols , COMMAND AND CONTROL , T1071.001 , T1071

References

1. https://www.intel471.com/blog/threat-hunting-case-study-medusa-ransomware

2. https://www.ransomware.live/group/medusa

3. https://www.cisa.gov/news-events/cybersecurity-advisories/aa25-071a

4. https://www.microsoft.com/en-us/security/blog/2025/10/06/investigating-active-exploitation-of-cve-2025-10035-goanywhere-managed-file-transfer-vulnerability/

5. https://zensec.co.uk/blog/how-rmm-abuse-fuelled-medusa-dragonforce-attacks/

6. https://www.checkpoint.com/cyber-hub/threat-prevention/ransomware/medusa-ransomware-group/

7. https://cyberpress.org/medusa-ransomware-attacks-spike-42/

8. https://blog.barracuda.com/2025/02/25/medusa-ransomware-and-its-cybercrime-ecosystem

10. https://www.cyberdaily.au/security/10021-more-monster-than-myth-unpacking-the-medusa-ransomware-operation

11. https://unit42.paloaltonetworks.com/medusa-ransomware-escalation-new-leak-site/

12. https://www.bitdefender.com/en-us/blog/businessinsights/medusa-ransomware-a-growing-threat-with-a-bold-online-presence

13. https://redpiranha.net/news/medusa-ransomware-everything-you-need-know

14.  https://www.theregister.com/2025/03/13/medusa_ransomware_infects_300_critical/

15. https://www.s-rminform.com/latest-thinking/cyber-threat-advisory-medusa-and-the-simplehelp-vulnerability

16. https://nagomisecurity.com/medusa-ransomware-us-cert-alert

17. https://arcticwolf.com/resources/blog/arctic-wolf-observes-campaign-exploiting-simplehelp-rmm-software-for-initial-access/

18. https://securityboulevard.com/2025/04/medusa-ransomware-inside-the-2025-resurgence-of-one-of-the-internets-most-aggressive-threats/

19. https://thehackernews.com/2025/03/medusa-ransomware-hits-40-victims-in.html

20.  https://www.quorumcyber.com/threat-intelligence/critical-alert-medusa-ransomware-threat-highlighted-by-fbi-cisa-and-ms-isac/

21. https://brandefense.io/blog/stone-gaze-in-depth-analysis-of-medusa-ransomware/

22. https://www.darktrace.com/ja/blog/2025-cyber-threat-landscape-darktraces-mid-year-review

23. https://www.joesandbox.com/analysis/1576447/0/html

24. https://blog.barracuda.com/2025/02/25/medusa-ransomware-and-its-cybercrime-ecosystem

25. https://shassit.mit.edu/news/medusa-ransomware-attacks-on-gmail/

26. https://thehackernews.com/2025/03/medusa-ransomware-uses-malicious-driver.html

27. https://www.cisa.gov/news-events/cybersecurity-advisories/aa25-163a

28. https://www.catonetworks.com/blog/cato-ctrl-investigation-of-rmm-tools/

29. https://redcanary.com/threat-detection-report/trends/rmm-tools/

30. https://www.proofpoint.com/us/blog/threat-insight/remote-monitoring-and-management-rmm-tooling-increasingly-attackers-first-choice

Inside the SOC
Darktrace cyber analysts are world-class experts in threat intelligence, threat hunting and incident response, and provide 24/7 SOC support to thousands of Darktrace customers around the globe. Inside the SOC is exclusively authored by these experts, providing analysis of cyber incidents and threat trends, based on real-world experience in the field.
Written by
Signe Zaharka
Principal Cyber Analyst

More in this series

No items found.

Blog

/

Network

/

July 28, 2026

Hiding in Plain Sight: Uncovering a Multi-Stage Ransomware Attack Through Behavioral Detection

Default blog imageDefault blog image

Why ransomware has changed

Ransomware attacks have continued to increase globally, with 698 incidents reported in May 2026, representing a 48% rise compared to 472 incidents in May 2025 [1]. At the same time, the ransomware landscape is evolving. Several major ransomware groups, including LockBit [2], have been disrupted by successful joint law enforcement operations, resulting in a shift away from a small number of dominant actors towards a more fragmented and distributed ecosystem. This is increasingly composed of smaller groups who play a specialized role in the attack, such as initial access brokers, affiliates or developers.

As a result, ransomware tactics, techniques, and procedures (TTPs) are becoming more diverse and less predictable. On top of this, adversaries are leveraging native tools and legitimate penetration testing frameworks to evade detection. Anomaly-based detection is therefore critical to identify pre-ransomware activity, rather than relying on signatures associated with a handful of well-known ransomware groups.

As these attacks often unfold over several days, there is a critical window for defenders to act. In this context, behavioral-based detection plays a vital role in identifying suspicious pre-ransomware activity, and enabling early intervention before encryption or exfiltration occurs.

Inside a modern ransomware intrusion

In early 2026, Darktrace detected activity within a customer’s environment related to a multi-stage ransomware intrusion from the initial compromise. This activity does not appear to be attributable to a specific ransomware group, and no known ransomware payload was observed until the final stage.

The attack aligns with a broader industry trend in which compromised virtual private network (VPN) credentials are used as an entry point, followed by rapid internal reconnaissance and lateral movement using legitimate administrative tools. This growing preference for native tools and legitimate frameworks in cyber-attacks illustrates that it is increasingly unreliable to depend solely on traditional indicators of compromise such as known malware signatures or exploit detection.

The intrusion also involved the use of Sliver, an open-source adversary emulation framework, which is increasingly observed in real-world attacks. Originally designed for penetration testing and red teaming, Sliver has gained traction among threat actors as a stealthier alternative to more heavily signatured frameworks such as Cobalt Strike. As a legitimate framework, its use further complicates detection for security tools that rely on known malicious signatures.

Darktrace’s detection of a ransomware event in a customer’s environment

The initial compromise appears to have occurred via compromised credentials used over the VPN shortly before, or at the onset of the first indicators of suspicious activity. While it remains unclear as to how or when the threat actors gained access to these credentials, the use of initial access brokers (IABs) is a common feature of modern ransomware operations. This suggests that access to the environment may have been established several days or weeks beforehand.

The intrusion unfolded over three days, presenting multiple opportunities for early detection and intervention before ransomware deployment. The attack progressed through a compressed but structured sequence: initial access and reconnaissance were completed within hours, followed by privilege escalation and lateral movement the next day, and culminating in data exfiltration and encryption shortly thereafter. Throughout each stage, distinct behavioral anomalies emerged across the network providing clear indicators of malicious activity well before the ransomware was deployed.

While Darktrace’s Autonomous Response capability was enabled within the customer’s environment, it was not fully configured across the impacted devices, allowing the attack to progress to ransomware deployment. Had Autonomous Response been fully deployed across the affected systems, it could have taken targeted action against the earliest stages of malicious activity, potentially disrupting the intrusion before it escalated.

Figure 1: Timeline of the attack progression.

Day 1: Reconnaissance and privilege escalation

The threat actor gained access via compromised VPN credentials and initiated internal reconnaissance. Darktrace detected anomalous scanning behavior, including unusual port scanning activity and widespread network enumeration.

Specifically, Darktrace detected a high volume of east-west scanning activity across a broad range of ports, with TCP connections targeting ports 21, 80, 445, 4899 and 8080. Associated URIs suggested the use of Nmap, a widely used penetration testing tool. This highlights how attackers often leverage legitimate penetration testing tools for malicious reconnaissance, enabling them to blend into normal network activity and evade traditional signature-based detection methods.

Figure 2: Darktrace's detection of a sharp increase in anomalous internal connections, triggering multiple high-severity model alerts associated with reconnaissance activity.

Several devices were observed using administrative credentials to carry out privileged actions in a manner that was highly anomalous for the environment. This activity was accompanied by behavior consistent with SMB authentication scanning, suggesting efforts to identify and access additional systems. As the activity intensified, an increasing number of devices became involved, signalling lateral movement and further spread across the network.

Darktrace also identified privilege escalation through active directory (AD) replication abuse, specifically via the drsuapi::DRSGetNCChanges function. This technique allows an attacker with sufficient privileges to request directory replication data from a domain controller (DC), enabling them to extract credentials, including password hashes, without directly interacting with user accounts. Commonly associated with ‘DCSync’ attacks, this technique is frequently used to obtain highly privileged credentials and enable further escalation within an environment.

Figure 3: Darktrace’s detection of anomalous AD replication activity indicative of privilege escalation.

This activity was seen alongside the use of the now obsolete SMBv1, repeated NTLM authentication attempts using multiple variations of ‘Administrator’ credentials, reverse DNS scanning, and large-scale network scanning. Darktrace observed widespread use of SMBv1 across the customer’s environment, exposing a significant security weakness. As a legacy protocol with well-documented weaknesses, SMBv1 can be exploited to facilitate lateral movement, allowing the attackers to expand their access following initial compromise.

Day 3: Lateral Movement, Command & Control, and Exfiltration

Two days later, the attacker escalated privileges and expanded their foothold using living-off-the-land (LOTL) techniques such as PSExec, WMI, and RDP. Concurrently, Darktrace identified command-and-control (C2)-style communications consistent with the Sliver framework, alongside rare outbound connections to cloud infrastructure indicating potential data exfiltration. The volume and severity of observed activity increased as attack behavior intensified.

The device was observed conducting extensive lateral movement, leveraging LOTL techniques to evade detection. Activity included WMI execution (e.g. ExecQuery), DCE-RPC activity, SMB sessions and file writes, most of which were successful, as well as the deployment of PSEXESVC.exe via ADMIN$ shares and prolonged RDP sessions. Darktrace identified this behavior as highly anomalous for the environment. Such activity is commonly associated with the transfer of attacker tooling, remote command execution, and the establishment of persistent access across compromised systems.  

Figure 4: Darktrace’s detection of a spike in RPC binding events indicative of potential lateral movement.

On the same day, Darktrace detected C2-style SSL communications originating from multiple internal devices to rare external endpoints. These connections exhibited anomalous characteristics, including invalid SSL certificates and repeated connection patterns resembling beaconing. Analysis of the observed JA3 fingerprint further linked the activity to Sliver, the adversary simulation framework referenced earlier, as the hash has previously been associated with Sliver-related infrastructure [3]. The use of this framework reflects a broader trend of attackers repurposing legitimate offensive security tools for stealthy C2 communications. Connections to 137[.]220[.]59[.]55 (ASN AS20473 AS-VULTR) indicated that the communications were likely routed via a virtual private server (VPS) hosted by Vultr. Attackers often utilize VPS infrastructure from legitimate cloud providers like Vultr to obscure their true origin, blend into benign traffic, and evade IP-based detection mechanisms [4].

Figure 5: Darktrace’s Cyber AI Analyst detection of two linked unusual connections to Vultr infrastructure.

Darktrace also observed a device initiating SSL connections to safedata.s3[.]wasabisys[.]com, an endpoint associated with Wasabi cloud storage. Darktrace recognized that neither the destination nor the associated IP address had previously been observed within the environment.  More than 200 MB of data was subsequently uploaded externally to endpoints sharing the same JA3 client hash, indicating a sustained transfer session and potential data exfiltration to third-party storage. The apparent exfiltration prior to encryption is consistent with a double-extortion ransomware strategy.

Figure 6: Darktrace’s Cyber AI Analyst detection of more than 30 rare outbound connections to a Wasabi cloud storage endpoint, indicative of potential data exfiltration

Day 4: Encryption

The attack culminated in ransomware deployment, marking the transition from suspicious network activity to a business-impacting incident. Using SMB-based propagation, the threat actor encrypted thousands of files across the network, affecting multiple systems and disrupting normal operations. Throughout the encryption event, the legacy SMBv1 protocol was used extensively across multiple internal systems, resulting in a significant increase in newly encrypted files.

Figure 7: Darktrace’s detection of abnormal spikes in SMB activity and associated model alerts, indicative of ransomware encryption and propagation.

Darktrace’s Cyber AI Analyst automatically investigated and correlated the encryption activity and related events into a single incident narrative, providing the customer with real-time visibility into the attack while significantly reducing investigation time.

Figure 8: Darktrace’s Cyber AI Analyst’s investigation into the encryption activity. AI Analyst incident detailing example encryption activity in real time. Related events are automatically correlated and summarized into a clear narrative, reducing investigation time.

Defender action recommendations

What Could Have Stopped the Attack Earlier?

Although the attack ultimately resulted in ransomware deployment, there were multiple opportunities to detect, contain, and disrupt the intrusion before encryption occurred. The following actions could have significantly reduced the overall impact:

Detect and investigate indicators of reconnaissance and lateral movement

  • Unusual scanning
  • Active Directory replication anomalies consistent with DCSync activity
  • Anomalous use of native tools and processes indicative of LOTL attacks
  • Unusual use of common reconnaissance tools such as Nmap and NetScan

Contain compromised credentials and affected devices

  • Disable and reset compromised VPN credentials
  • Isolate devices performing anomalous scanning and lateral movement activity

Block suspicious external communications and data exfiltration

  • Use anomaly-based detection to detect and block repeated outbound connections to rare external infrastructure
  • Prevent data exfiltration to unauthorized cloud storage services such as Wasabi

Conclusion

The incident highlights the importance of anomaly-based detection, particularly against attacks that primarily use native or legitimate tools to evade traditional security measures. Darktrace identified suspicious activity from the first day of the compromise, providing multiple opportunities to disrupt the intrusion before it progressed to lateral movement and data exfiltration.

In this instance, detection was not the limiting factor; response time was. Prompt investigation and containment of devices exhibiting anomalous behavior could have prevented lateral movement, data exfiltration, and ultimately ransomware deployment.

As adversaries increasingly prioritize stealth over custom malware, relying instead on legitimate tools, valid credentials, and trusted infrastructure, traditional signature-based detection becomes less effective. Identifying subtle behavioral deviations early remains critical to disrupting attacks before they escalate into full-scale ransomware incidents.

Credit to Alexandra Evzona (Cyber Analyst), Priya Thapa (Senior Cyber Analyst)
Edited by Ryan Traill (Content Manager)

Appendices

References

[1] https://industrialcyber.co/ransomware/check-point-reports-ransomware-attacks-jump-48-year-over-year-despite-decline-in-overall-cyberattack-activity/

[2] https://www.europol.europa.eu/media-press/newsroom/news/law-enforcement-disrupt-worlds-biggest-ransomware-operation

[3] https://fieldeffect.com/blog/field-effect-mitigates-not-so-simplehelp-exploits-enabling-deployment-of-backdoors

[4] https://www.darktrace.com/blog/from-vps-to-phishing-how-darktrace-uncovered-saas-hijacks-through-virtual-infrastructure-abuse

Indicators of Compromise (IoCs)

IP Addresses

  • 137[.]220[.]59[.]55 – Potential C2 infrastructure (Vultr AS20473)
  • 38[.]27[.]106[.]123 – Wasabi cloud storage endpoint associated with potential data exfiltration
  • 38[.]27[.]106[.]128 – Wasabi cloud storage endpoint associated with potential data exfiltration
  • 38[.]27[.]106[.]117 – Wasabi cloud storage endpoint associated with potential data exfiltration

Domains

  • safedata[.]s3[.]wasabisys[.]com – Potential data exfiltration endpoint
  • *.wasabisys[.]com – Associated Wasabi cloud storage infrastructure

JA3 Fingerprint

  • d6828e30ab66774a91a96ae93be4ae4c – Associated with the Sliver adversary emulation framework

Files

  • Delete[.]me – File observed during reconnaissance activity, commonly associated with NetScan

Darktrace Model Coverage

·       Anomalous Connection / Active Remote Desktop Tunnel

·       Anomalous Connection / Anomalous Remote Registry Service Control

·       Anomalous Connection / Multiple Failed Windows UDP

·       Anomalous Connection / New or Uncommon Service Control

·       Anomalous Connection / New or Uncommon Service Enumeration

·       Anomalous Connection / New User Agent to IP Without Hostname

·       Anomalous Connection / SMB Enumeration

·       Anomalous Connection / Suspicious Activity On High Risk Device

·       Anomalous Connection / Suspicious Read Write Ratio

·       Anomalous Connection / Sustained MIME Type Conversion

·       Anomalous Connection / Uncommon 1 GiB Outbound

·       Anomalous Connection / Unusual Admin RDP Session

·       Anomalous Connection / Unusual Admin SMB Session

·       Anomalous Connection / Unusual SMB Version 1 Connectivity

·       Anomalous File / EXE from Rare External Location

·       Anomalous File / Internal / Additional Extension Appended to SMB File

·       Anomalous Server Activity / Outgoing from Server

·       Compromise / Beaconing Activity To External Rare

·       Compromise / Ransomware / Possible Ransom Note Read

·       Compromise / Ransomware / Ransom or Offensive Words Written to SMB

·       Compromise / Ransomware / Suspicious SMB Activity

·       Device / Anonymous NTLM Logins

·       Device / Attack and Recon Tools

·       Device / Initial Attack Chain Activity

·       Device / Large Number of Model Alerts

·       Device / Long Agent Connection to New Endpoint

·       Device / Multiple Lateral Movement Model Alerts

·       Device / Network Scan

·       Device / New or Uncommon SMB Named Pipe

·       Device / New or Unusual Remote Command Execution

·       Device / New User Agent

·       Device / Possible RPC Lateral Movement

·       Device / Possible SMB/NTLM Brute Force

·       Device / RDP Scan

·       Device / SMB Lateral Movement

·       Device / SMB Session Brute Force (Non-Admin)

·       Device / SMB Version 1 Access Failures

·       Device / Suspicious File Delete Activity

·       Device / Suspicious Network Scan Activity

·       Device / Unusual SMB Error Detected

·       Device / Unusual SMB To Critical Resource

·       Device / Unusual Winreg Operation

·       Unusual Activity / Multiple Failed Internal Connections

·       Unusual Activity / Possible RPC Recon Activity

·       Unusual Activity / Sustained Anomalous SMB Activity

·       Unusual Activity / Unusual External Data to New Endpoint

·       Unusual Activity / Unusual External Data Transfer

·       Unusual Activity / Unusual File Storage Data Transfer

·       Unusual Activity / Unusual Large Internal Transfer

·       User / New Admin Credentials on Client

·       User / NTLM Login from Unauthenticated Device

Autonomous Response Model Alerts

·       Antigena / Network / External Threat / Antigena Ransomware Block

·       Antigena / Network / External Threat / Antigena Suspicious File Block

·       Antigena / Network / Insider Threat / Antigena Active Threat SMB Write Block

·       Antigena / Network / Insider Threat / Antigena Internal Anomalous File Activity

·       Antigena / Network / Insider Threat / Antigena Large Data Volume Outbound Block

·       Antigena / Network / Insider Threat / Antigena Network Scan Block

·       Antigena / Network / Insider Threat / Antigena Unusual Privileged User Activities Block

·       Antigena / Network / Manual / Quarantine Device

·       Antigena / Network / Significant Anomaly / Antigena Alerts Over Time Block

·       Antigena / Network / Significant Anomaly / Antigena Controlled and Model Alert

·       Antigena / Network / Significant Anomaly / Antigena Enhanced Monitoring from Client Block

·       Antigena / Network / Significant Anomaly / Antigena Enhanced Monitoring from Server Block 100

·       Antigena / Network / Significant Anomaly / Antigena Significant Anomaly from Client Block

MITRE ATT&CK MAPPING

Command and control - Protocol Tunneling - T1572

Command and control – Web Protocols – T1071.001

Credential Access- Exploitation for Credential Access- T1212

Credential Access- Password Guessing- T1110

Discovery- File and Directory Discovery- T1083

Discovery- Network Service Discovery- T1046

Discovery- Network Share Discovery- T1135

Discovery- Remote System Discovery- T1018

Exfiltration- Exfiltration Over C2 Channel- T1041

Exfiltration- Exfiltration to Cloud Storage- T1567

Impact- Data Encrypted for Impact- T1486

Impact- Data Encrypted for Impact- T1486

Impact- Service Stop - T1489

Initial Access- Public-Facing Application- T1190

Lateral Movement- Exploitation of Remote Services- T1210

Lateral Movement- Remote Desktop Protocol- T1021

Lateral Movement- SMB/Windows Admin Shares- T1021

Lateral Movement- Taint Shared Content- T1080

Persistence- Modify Registry- T1112

Privilege Escalation- Exploitation for Privilege Escalation- T0890

Privilege Escalation- Valid Accounts- T1078

Reconnaissance- Scanning IP Blocks- T1595

Reconnaissance- Vulnerability Scanning- T1595

Resource Development- Malware- T1588

Stealth- File Deletion- T1070

Continue reading
About the author
Alexandra Evzona
Cyber Analyst

Blog

/

Email

/

July 28, 2026

Darktrace / EMAIL Expands Behavioral Defense Across Email and Collaboration Workflows

Default blog imageDefault blog image

Email and collaboration tools do more than carry messages. They are where organizations approve payments, share sensitive data, reset credentials, and make thousands of everyday decisions. Increasingly, they are interfaces through which humans direct AI agents in their daily activity. Email, Slack and Teams are high volume, rich with sensitive data, and an easy place to hide malicious activity.

The opportunity isn’t lost on bad actors. Darktrace / EMAIL detected more than 32 million high-confidence phishing emails globally in 2025, and 70% of those messages passed DMARC authentication.  Phishing is increasingly difficult to detect and familiar trust signals alone are not enough. People and security teams need to understand how a message fits the normal behavior of the sender, recipient, and organization. They also need to correlate activity across platforms to spot threats that span multiple channels.

To effectively secure against today’s evolved threats, security teams need to act at two levels: they need to help each employee make a safer decision ‘in the moment’, and they need to understand the wider patterns that may expose the business to risk.

Darktrace is introducing four new capabilities in Darktrace / EMAIL to address both challenges. The new features explain suspicious content more clearly to end users, strengthen the capabilities of Darktrace / Adaptive Human Defense with richer guidance, let organizations define their own patterns for detecting sensitive data in messages, and give security teams a process-level view of risk across email and collaboration workflows.

Darktrace / EMAIL Inbox Analysis highlights risky content within your emails

A warning is more useful when it explains what the user should look at. To help do that, we’ve expanded Darktrace / EMAIL’s Inbox Analysis Add-In to highlight potentially dangerous content within the body of emails that Darktrace / EMAIL flags as potentially suspicious or high risk.  

The add-in can highlight language designed to create urgency, financial references, requests for payment, suspicious links, and content that is unusual for the sender. Each highlighted element includes a pop up that explains why it may be suspicious. Instead of asking an employee to accept a verdict without context, the analysis helps them examine the message and make a more informed decision.

Enhanced Just-In-Time Training Banners in Darktrace / Adaptive Human Defense

Enhanced Just-In-Time Training Banners build on the same principle. The banners now include a contextual header, actionable advice, and specific detection context. This gives employees more useful guidance at the point of risk without adding unnecessary information or cognitive load.

Together, the capabilities help turn a warning into a short learning moment. Employees can see what looks unusual, understand what action to take, and build their judgment.

Custom Sensitive Data Detection in Darktrace / EMAIL - Data Loss Prevention

Sensitive data is different for every business. Standard categories such as payment card details or government identifiers matter, but organizations also have their own customer codes, project names, research formats, account structures, and internal identifiers.

Custom Sensitive Data Detection in Darktrace / EMAIL - Data Loss Prevention allows administrators to write custom expressions for the data their organization needs to protect. Matched content can trigger existing model actions and data loss prevention (DLP) workflows, extending Darktrace's DLP capabilities.

This extends data loss detection beyond a fixed library of common data types. Security teams can apply controls to information that is sensitive in the context of their own organization and adapt those controls as the business changes.

Introducing Email and Collaboration Workflow Risk Posture Dashboards

Some of the most important risks are not isolated events. They are repeated ways of working that create an opening for error, misuse, or attack. For example, a payment request may be one suspicious message, but a recurring approval workflow that relies on weak verification is a business process risk.

The new Email and Collaboration Workflow Risk Posture Dashboard analyzes email and collaboration data across Email, Microsoft Teams, Slack and Zoom to provide a process-level view of risk in the organization. These may include financial authorization workflows, sensitive data sharing patterns, and activity that could expose credentials.

The dashboard brings these patterns into a view and provides actionable recommendations. This helps security teams determine where to investigate or strengthen controls, where ownership needs to be clarified, and where the business may need to change a risky process. It gives CISOs a clearer view of how human and communication risk is embedded in everyday operations, not only where individual alerts occur.

Behavior connects the individual decision to the wider risk

These capabilities build on Darktrace’s unique behavioral approach to security. We use Adaptive AI to learn how people and AI normally behave within an organization, creating the context needed to recognize when activity changes.

Within the Darktrace Behavioral Defense Platform, Darktrace / EMAIL helps protect people against phishing, account takeover, data exfiltration, and human risk across email and collaboration tools. The new capabilities extend that protection in both directions. They give employees clearer context for the decision in front of them, while giving security leaders a broader view of the workflows and behavior that create risk across the organization.

The result is not simply more alerts. It is a better understanding of why something is risky, what action to take, and where the organization can reduce risk before a familiar process becomes an easy route for an attacker.

[related-resource]

Continue reading
About the author
Carlos Gray
Senior Product Marketing Manager, Email
あなたのデータ × DarktraceのAI
唯一無二のDarktrace AIで、ネットワークセキュリティを次の次元へ