Security

Parallel Threat Activity: Microsoft DART Findings

3 min read

Summary

Microsoft Incident Response detailed a complex intrusion in which two unrelated threat actors operated simultaneously in the same environment, complicating attribution and detection. The case highlights how ransomware activity, SharePoint exploitation, trusted tool abuse, and identity compromise can overlap across hybrid estates, reinforcing the need for strong telemetry, patching, and coordinated response.

Need help with Security?Talk to an Expert

Introduction

Microsoft’s latest Cyberattack Series report shows why modern incident response is getting harder: defenders may be dealing with more than one attacker at the same time. In this case, Microsoft DART uncovered a single intrusion that involved parallel activity from two unrelated threat actors, creating overlapping signals that complicated both attribution and containment.

For security teams, the lesson is clear: isolated alerts may not reflect the full scope of an attack, especially in hybrid environments spanning on-premises and cloud resources.

What’s new in the report

Two threat actors in one intrusion

  • Microsoft DART found evidence of two separate threat actors operating simultaneously in the same compromised environment.
  • One actor, Storm-2603, was linked to ransomware-related activity and targeting of on-premises SharePoint servers.
  • A second actor used DLL sideloading and custom backdoors, indicating a distinct intrusion path and tradecraft.

SharePoint and reconnaissance activity

  • Storm-2603 had reportedly targeted SharePoint servers since mid-2025.
  • The actor exploited known vulnerabilities and also probed for additional entry points using requests for files such as win.ini and web.config, consistent with reconnaissance for local file inclusion weaknesses.

Trusted tools used for persistence

  • The attackers used legitimate tools to blend into normal admin activity, including:
    • Velociraptor with SYSTEM privileges
    • Cloudflare tunnels
    • Zoho Assist
    • SSH via Visual Studio Code
  • Additional tactics included creating new local and domain admin accounts and using a vulnerable driver to tamper with memory and weaken protections.

Why this matters for IT and security administrators

This report is a reminder that trusted tools and normal-looking admin behavior can mask malicious activity. Security teams managing Microsoft environments should pay close attention to internet-facing SharePoint systems, privileged account creation, remote access tooling, and telemetry correlation across identities, endpoints, and cloud services.

The case also shows why ransomware investigations should not assume a single actor or a linear attack chain. Parallel threat activity can hide the true scope of compromise and delay containment if teams investigate alerts in isolation.

  • Patch internet-facing systems quickly, especially on-premises SharePoint servers.
  • Centralize and retain telemetry across endpoints, identities, and cloud resources.
  • Review use of trusted admin tools such as remote access software, tunneling tools, and forensic utilities.
  • Audit privileged account changes and investigate unexpected local or domain admin creation.
  • Test incident response playbooks to ensure teams can isolate compromised users, devices, and access paths quickly.

Organizations that improve visibility, identity protections, and response coordination will be better positioned to detect and contain complex multi-actor intrusions earlier.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Microsoft SecurityDARTSharePoint securityransomwareincident response

Related Posts

Security

Microsoft Digital Defense Report 2026: Key Security Insights

Microsoft's 2026 Digital Defense Report highlights how AI and growing system interconnectedness are reshaping both cyberattacks and defense strategies. The report emphasizes that organizations must secure AI, identities, data, and cloud environments together while improving signal correlation across tools to detect modern threats faster.

Security

Government Cyber Risk in 2026: Microsoft’s 5 Priorities

Microsoft says government agencies were the most targeted sector in 2026, accounting for 27% of observed cyber threat activity. The company urges public-sector leaders to focus on five resilience priorities, including faster response, AI security, bidirectional information sharing, and planning for incidents that spread across suppliers and essential services.

Security

Microsoft Ignite 2026 Security Guide: Key Sessions

Microsoft has published its security guide for Microsoft Ignite 2026, highlighting AI-first security themes, a dedicated Security Pre-Day, and technical sessions focused on securing identities, data, devices, clouds, and AI agents. For IT and security teams, the event offers an early look at Microsoft’s roadmap and practical guidance for building an AI-ready security strategy.

Security

CVE-2026-73570: Zimbra Mail Server Exploitation

Microsoft is tracking active exploitation of CVE-2026-73570, an unauthenticated command injection flaw affecting internet-facing Zimbra mail servers with the optional zimbra-snmp package installed and SNMP notifications enabled. The issue can lead to web shell deployment, privilege escalation, mailbox data theft, and persistent remote access, making immediate patching and configuration review critical for administrators.

Security

Phishing Abuses RMM Tools for Persistent Access

Microsoft security researchers observed phishing campaigns in July 2026 that used a legitimate MSP360 RMM installer disguised as meeting invites, PDF updates, and other lures to gain remote access. Attackers then deployed ConnectWise ScreenConnect for redundant persistence, highlighting the need for tighter controls on remote management tools and better detection of unapproved RMM activity.

Security

Azure DevOps Attack Path Exposed in New DART Report

Microsoft’s latest DART cyberattack report shows how a single compromised identity was used to access Azure DevOps, alter pipelines, and harvest Kubernetes credentials. The case highlights how tightly connected identity, DevOps, and cloud environments can let attackers move far beyond source code, making stronger identity and pipeline controls essential.