Security

Microsoft Teams Vishing Attacks via Quick Assist

3 min read

Summary

Microsoft warned that a recent attack used Teams-based voice phishing to impersonate IT support, trick an employee into approving a Quick Assist session, and then steal credentials, deploy malware, and expand access using legitimate Windows tools. The incident matters because it shows how attackers can bypass traditional patch-focused defenses by exploiting trust in everyday collaboration and remote support workflows, making stronger identity protections, user verification, and remote-access controls essential.

Need help with Security?Talk to an Expert

Introduction

Microsoft’s latest Cyberattack Series report is a timely warning for security teams: attackers do not always need an unpatched vulnerability to gain access. In this case, a threat actor used Microsoft Teams voice phishing, impersonated IT support, and convinced an employee to allow remote access through Quick Assist—turning routine collaboration and support workflows into an entry point.

What happened

According to Microsoft Incident Response (DART), the attack began with persistent vishing over Microsoft Teams. After two unsuccessful attempts, the attacker persuaded a third employee to approve a Quick Assist session.

Once connected, the threat actor moved quickly:

  • Directed the user to a malicious website controlled by the attacker
  • Captured corporate credentials through a spoofed sign-in form
  • Downloaded multiple malicious payloads onto the device
  • Used a disguised MSI package to sideload a malicious DLL
  • Established command-and-control using trusted Windows mechanisms
  • Expanded access with encrypted loaders, remote command execution, credential harvesting, and session hijacking

Microsoft noted that the attacker relied heavily on legitimate administrative tooling and techniques designed to blend in with normal enterprise activity.

Why this matters for IT and security teams

This incident reflects a growing identity-first attack pattern where trust is the primary target. Collaboration platforms such as Teams can be abused to create urgency and legitimacy, especially when users believe they are interacting with internal support staff.

For administrators, the key takeaway is that built-in tools like Quick Assist and common remote management utilities can become high-risk when governance is weak. Traditional defenses focused mainly on malware signatures or exploit detection may miss early-stage social engineering and hands-on-keyboard activity.

Microsoft’s response

DART confirmed the compromise originated from a successful Teams vishing interaction and acted to contain the threat before it could expand further. Microsoft reports that:

  • The activity was short-lived and limited in scope
  • Responders focused on protecting privileged assets and limiting lateral movement
  • Forensic analysis found no persistence mechanisms remained
  • The attacker’s broader objectives were not achieved

Organizations should review both collaboration and remote access controls immediately:

  • Restrict inbound Teams communications from unmanaged external accounts
  • Consider allowlisting trusted external domains for Teams contact
  • Inventory remote monitoring and remote support tools in use
  • Remove or disable Quick Assist where it is not required
  • Train users to verify IT support requests through approved internal channels
  • Monitor for suspicious use of legitimate admin tools and unusual remote sessions

Bottom line

This report is a clear reminder that modern intrusions often begin with persuasion, not exploitation. Security teams should harden Teams external access, reduce unnecessary remote support tooling, and strengthen user verification processes to make trust-based attacks harder to execute.

Need help with Security?

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

Talk to an Expert

Stay updated on Microsoft technologies

SecurityMicrosoft TeamsQuick Assistvishingincident 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.