Microsoft: Storm-2570 Affiliate Uses Same TTPs for Qilin, DragonForce

Microsoft Links Ransomware Affiliate Storm-2570 to Four Malware Families

HIGH
September 25, 2026
5m read
Threat ActorRansomwareMalware

Related Entities

Threat Actors

Storm-2570

Organizations

Products & Tech

MeshAgentAteraNinjaRMMScreenConnectRclones5cmdPsExec ImpacketNetExec

Other

Qilin DragonForceAnubis BERTMimikatz LaZagne

Full Report

Executive Summary

Microsoft has identified and detailed the consistent operational playbook of a single ransomware affiliate, tracked as Storm-2570. This group is linked to attacks deploying at least four distinct ransomware families: Qilin, DragonForce, Anubis, and BERT. The research, published on September 24, 2026, underscores a critical defensive principle: tracking the consistent tactics, techniques, and procedures (TTPs) of the human operator provides more durable detection opportunities than focusing on the ever-changing final ransomware payload. Storm-2570's methodology involves abusing legitimate remote management tools, harvesting credentials, disabling security controls, and exfiltrating data before encryption, offering multiple chances for defenders to intervene.


Threat Overview

Storm-2570 is a prolific ransomware affiliate active since at least April 2025. By operating under multiple Ransomware-as-a-Service (RaaS) banners, the group complicates attribution and defense. However, Microsoft's analysis reveals a highly consistent set of post-compromise behaviors, creating a distinct fingerprint for the attacker.

The group has targeted a wide range of sectors, including healthcare, education, energy, and manufacturing, with victims located in the United States, Canada, the United Kingdom, Spain, the Netherlands, and Puerto Rico. While the initial access vector is not yet confirmed, their actions after gaining a foothold are well-documented and predictable.

Technical Analysis

Storm-2570's attack lifecycle is characterized by the use of legitimate tools and common offensive security utilities, a 'living-off-the-land' approach mixed with custom tooling.

  • Command and Control: The affiliate heavily relies on remote management and monitoring (RMM) software for persistence and C2. Tools observed include MeshAgent, Atera, NinjaRMM, and ScreenConnect. They often rename the executables to masquerade as legitimate software (T1105 - Ingress Tool Transfer).
  • Credential Access: Storm-2570 uses a variety of tools to harvest credentials, including Mimikatz, LaZagne, and pypykatz. Critically, they have been observed using the native Windows utility ntdsutil to create a copy of the Active Directory database (ntds.dit), which is then taken offline for credential extraction (T1003.003 - NTDS).
  • Defense Evasion: The group actively works to undermine security measures, including using commands to disable Microsoft Defender's real-time protection (T1562.001 - Disable or Modify Tools).
  • Lateral Movement: Tools like PsExec, Impacket, and NetExec are used to move across the network to other systems.
  • Exfiltration: Before deploying ransomware, the group exfiltrates stolen data using tools like s5cmd and Rclone to upload archives to attacker-controlled cloud storage (T1567.002 - Exfiltration to Cloud Storage).
  • Impact: The final step is the deployment of one of the associated ransomware payloads, such as Qilin, to encrypt files across the network (T1486 - Data Encrypted for Impact).

Impact Assessment

By targeting diverse and critical sectors, Storm-2570 poses a significant economic and operational threat. The consistent TTPs across different ransomware brands suggest a skilled and efficient operator capable of systematically compromising networks. The impact on a victim organization includes not only the cost of the ransom and recovery but also the damage from the public leak of sensitive data stolen during the exfiltration phase. The focus on healthcare and energy sectors is particularly concerning due to the potential for disruption of essential services.

IOCs — Directly from Articles

No specific file hashes, IP addresses, or domains were mentioned in the source articles.

Cyber Observables — Hunting Hints

Security teams should hunt for the following TTP-based observables:

Type
process_name
Value
MeshAgent.exe, AteraAgent.exe, NinjaRMM.exe
Description
Presence of legitimate RMM tools in environments where they are not officially used.
Type
command_line_pattern
Value
ntdsutil.exe "ac i ntds" "ifm" "create full C:\temp"
Description
Command to create an Install From Media (IFM) copy of the Active Directory database.
Type
command_line_pattern
Value
rclone.exe copy /path/to/data remote:bucket
Description
Use of Rclone to exfiltrate data to cloud storage providers.
Type
command_line_pattern
Value
Set-MpPreference -DisableRealtimeMonitoring $true
Description
PowerShell command used to disable Microsoft Defender.
Type
process_name
Value
s5cmd.exe
Description
Presence and execution of the s5cmd tool, used for high-speed S3 data transfers.

Detection & Response

  • Monitor RMM Tools: Establish a baseline of approved remote administration tools. Alert on the installation or execution of any unauthorized RMM software. Use D3FEND's D3-EAL: Executable Allowlisting to prevent unapproved tools from running.
  • Protect Active Directory: Closely monitor for any use of ntdsutil.exe. Access to the ntds.dit file should be heavily restricted and logged. Alert on any process attempting to access or copy this file. D3-DAM: Domain Account Monitoring is a key defensive technique.
  • Egress Traffic Filtering: Monitor and filter outbound network traffic. The use of tools like Rclone and s5cmd creates distinctive traffic patterns to cloud storage providers that can be detected and blocked. D3-OTF: Outbound Traffic Filtering can prevent data exfiltration.

Mitigation

  • Application Control: Implement application control policies to restrict the execution of unauthorized software, including unapproved RMM tools and known credential dumping utilities.
  • Harden Active Directory: Secure privileged accounts, implement robust password policies, and restrict access to domain controllers. Follow best practices for securing AD against attacks like Kerberoasting and DCSync.
  • Endpoint Protection: Ensure endpoint security solutions are properly configured, tamper protection is enabled, and alerts for disabling security features are treated with high priority.
  • Network Segmentation: Segment the network to inhibit lateral movement, making it harder for an attacker to move from a compromised workstation to a critical server like a domain controller.

Timeline of Events

1
April 1, 2025
Storm-2570 affiliate activity is first observed.
2
September 24, 2026
Microsoft publishes its threat intelligence report on Storm-2570's consistent TTPs.
3
September 25, 2026
This article was published

MITRE ATT&CK Mitigations

Use application allowlisting to prevent the execution of unauthorized RMM tools and other attacker utilities.

Mapped D3FEND Techniques:

Audit

M1047enterprise

Enable and monitor command-line and PowerShell logging to detect suspicious commands like `ntdsutil` or attempts to disable security software.

Mapped D3FEND Techniques:

Implement egress filtering to block outbound connections to known malicious destinations and unauthorized cloud storage services.

Mapped D3FEND Techniques:

Harden Active Directory by restricting permissions and closely monitoring for any attempts to access or copy the ntds.dit file.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

To directly counter Storm-2570's abuse of legitimate RMM tools like MeshAgent and Atera, organizations should implement a strict application allowlisting policy. This involves creating an inventory of all approved software and configuring endpoint security tools (like AppLocker or third-party solutions) to block the execution of any application not on this list. This is particularly critical on servers and domain controllers. By defining a 'known good' baseline, the execution of unauthorized RMM agents, credential dumpers like Mimikatz, and exfiltration tools like Rclone would be prevented by default. This shifts the defensive posture from chasing known bad signatures to enforcing known good behavior, significantly raising the difficulty for the attacker to establish persistence and execute their toolset.

Storm-2570's use of ntdsutil to steal the Active Directory database is a key, high-fidelity indicator of a major compromise. Defenders must implement specific monitoring for this activity. Configure SACLs (System Access Control Lists) on the ntds.dit file (%SystemRoot%\NTDS\ntds.dit) to log all access attempts and forward these logs to a SIEM. Create a high-priority alert that triggers any time ntdsutil.exe is executed on a domain controller, or any process other than lsass.exe attempts to read the ntds.dit file. This provides a critical tripwire that can detect the adversary during the credential access phase, before they have achieved full domain dominance and begun exfiltration.

Timeline of Events

1
April 1, 2025

Storm-2570 affiliate activity is first observed.

2
September 24, 2026

Microsoft publishes its threat intelligence report on Storm-2570's consistent TTPs.

Sources & References

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

Storm-2570ransomware affiliateQilinDragonForceTTPsMicrosoftRMMntdsutil

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

⚡ Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.