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 Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.