Security

Cross-Tenant Teams Impersonation Attack Playbook

3 min read

Summary

Microsoft has detailed a human-operated intrusion chain where attackers use cross-tenant Microsoft Teams chats to impersonate helpdesk staff and trick users into granting remote access through tools like Quick Assist. The campaign matters because it blends legitimate collaboration, remote support, and admin tools to enable lateral movement, persistence, and data exfiltration while appearing like normal IT activity.

Need help with Security?Talk to an Expert

Introduction

Microsoft has published new threat research describing how attackers are abusing external Microsoft Teams chats to impersonate IT or helpdesk staff. For IT and security teams, this is an important reminder that modern phishing and social engineering no longer start only with email—they can begin inside trusted collaboration tools and quickly escalate into enterprise-wide compromise.

What’s new

Microsoft’s report outlines a full human-operated intrusion playbook that starts with cross-tenant Teams messages and ends with data exfiltration.

Attack chain highlighted by Microsoft

  • Initial contact via Teams: Attackers pose as support personnel using external Teams communication.
  • Remote assistance foothold: Victims are convinced to launch Quick Assist or similar remote support tools and approve access.
  • Reconnaissance and validation: Attackers quickly check user privileges, system details, and access level.
  • Trusted app abuse: Vendor-signed applications are launched with attacker-supplied modules to run malicious code.
  • Command and control: Attackers establish persistent access while blending into normal admin activity.
  • Lateral movement: Native tools such as WinRM are used to pivot toward high-value assets, including domain controllers.
  • Follow-on tooling: Commercial remote management software like Level RMM may be deployed.
  • Data exfiltration: Utilities such as Rclone are used to stage and move sensitive data to external cloud storage.

Why this matters for administrators

This campaign is notable because it relies heavily on legitimate Microsoft and third-party tools rather than obvious malware. That makes detection harder and increases the chance that activity will look like routine IT support, remote administration, or user-approved actions.

The biggest risk is not just external Teams messaging itself, but the moment a user approves remote control. Once that happens, attackers can move quickly—often within minutes—to establish broader access, deploy tools, and target identity or domain infrastructure.

Administrators should review controls across collaboration, endpoint, and identity security:

  • Harden external Teams access and review cross-tenant communication policies.
  • Train users to treat unsolicited helpdesk or security contacts in Teams with suspicion, especially first-contact messages.
  • Restrict or monitor Quick Assist and other remote support tools where possible.
  • Watch for suspicious process chains such as QuickAssist.exe followed by cmd.exe or PowerShell.
  • Monitor lateral movement activity involving WinRM and unexpected remote management software.
  • Review data exfiltration signals tied to tools like Rclone or unusual cloud storage destinations.
  • Use Microsoft Defender XDR to correlate identity, endpoint, and Teams telemetry for earlier detection.

Bottom line

Microsoft’s research shows that collaboration platforms are now part of the active intrusion landscape. Security teams should treat Teams-based impersonation and user-approved remote assistance as high-risk pathways and update monitoring, user awareness, and response playbooks accordingly.

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 TeamsQuick AssistMicrosoft Defender XDRdata exfiltrationphishing

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.