The fake help desk inside Teams

Fake IT support on Microsoft Teams gains PC control and steals company data

From the HARD Situation Room · First reported
microsoft.com: From help desk impersonation to AD CS abuse: Investigating ESC1 and ESC8 intrusion paths | Microsoft Security Blog
Screenshot: microsoft.com

Microsoft investigated two intrusions that began with fake support messages and calls. Attackers used insecure company sign-in settings to expand their access; one case ended in data theft. Microsoft says no flaw in Teams was exploited.

What to do this week

  1. Verify through a contact you already trust.Call your saved IT number or open your usual support portal yourself. Confirm the request before joining a support call, sharing your screen or allowing remote control. Microsoft recommends a separate, known internal channel[9].
  2. Report the spam and the support approach together.Tell the real help desk if an inbox flood is followed by an unexpected offer of help. Treat an external sender claiming to be internal IT as a warning sign. Arctic Wolf describes this combination[2].
  3. If you allowed access, act immediately.End the remote session and contact your real IT team using another device. Explain what you approved and when. Microsoft’s advice is to disconnect a suspicious session and report it[5]; ask IT to investigate the wider company access too.
  4. Ask IT to limit who can reach staff.Review external Teams access[8], allowing only required partner domains and reviewing personal-account contact separately. Have IT restrict remote support to approved tools and workflows[9].
  5. Ask for a check of company sign-in security.If your organisation uses Active Directory Certificate Services, have IT review certificate permissions[10] and apply Microsoft’s secure configuration guidance[11]. Ask for confirmation of the findings and any changes needed.

A fake video meeting works the same way: a trusted name asks you to run something. See the FaceStealer fake video meeting scam.

What happened

Employees are being persuaded to hand over control of their PCs to people posing as IT support on Microsoft Teams. Microsoft’s 30 October report describes two intrusions, including one that ended in company data theft. Before allowing an unexpected caller onto your computer, check with your real help desk through a contact you already know. Microsoft’s investigation[1] explains what happened.

Separately, Arctic Wolf reported on 26 October[2] that it had examined more than 400 incidents involving abuse of Teams external chat. That figure should not be read as 400 breached companies: Arctic Wolf told Dark Reading[3] that roughly 15% of cases progressed to a successful compromise.

Teams support impersonationUnexpected help-desk chats and calls
HARD rating
High Verify before granting access.
Warning signs
A sudden spam flood, followed by an offer of IT help and a request for remote control.
Software involved
Microsoft Teams and remote-support tools, including Quick Assist.
Immediate response
End suspicious remote sessions and contact your real IT team.
What’s known. The warning pattern is described by Help Net Security[4]; the immediate response follows Microsoft’s Quick Assist guidance[5].
The full story3 more sections

Why the call feels plausible

In many cases Arctic Wolf examined, people received hundreds of unwanted subscription emails within minutes. A Teams message then offered to fix the problem the attackers had created. Some senders put “(Internal)” in their display name even while Teams labelled them external. Arctic Wolf’s findings[2] show the apparent help coming at the same time as the disruption.

Quick Assist is legitimate support software that can let another person see and control your computer. That does not establish who that person is. Microsoft advises[5] accepting help only after you have initiated contact with your support team. Separately, Cisco Talos’s 29 October report[6] described multiple investigations involving help-desk impersonation and calls persuading people to allow remote access.

The damage can spread beyond one PC

The attackers in Microsoft’s cases abused settings in Active Directory Certificate Services, a company system that issues digital certificates used to sign in. They obtained certificates for powerful accounts. These attacks did not exploit a Teams flaw. The Hacker News’s account of Microsoft’s findings[7] explains the distinction.

In the first case, an account excluded from automatic containment remained available and was used to steal files. In the second, the company isolated the affected PC after security alerts; Microsoft observed no further progression. Resetting a password alone does not revoke an issued certificate. Microsoft says recovery must also address certificates and existing sign-in tickets[1].

Who is affected

This warning matters wherever staff use Teams with outside organisations. Teams external access[8] allows those conversations, and all external domains are allowed by default. If you run a business or family office, include executives, assistants and anyone who may approve remote support in the briefing.

The published account does not name Microsoft’s affected companies or give the amount of data stolen. It does not establish that a particular family’s records were exposed. The reported limits[7] matter as much as the confirmed theft.

Timeline
  1. HARD publishes its article, at High.

References11
  1. ^ Microsoft Security (). “From help desk impersonation to AD CS abuse: Investigating ESC1 and ESC8 intrusion paths”. Primary investigation of two intrusions, their outcomes and certificate-aware recovery.
  2. ^ Arctic Wolf (). “Beyond the Inbox: How Threat Actors Abuse Microsoft Teams External Chat for Initial Access”. More than 400 incidents; spam floods, impersonation patterns and defensive recommendations.
  3. ^ Dark Reading (). “External Teams Chats Anchor 15-Minute Malware Delivery”. Arctic Wolf interview puts successful compromises at roughly 15% of cases.
  4. ^ Help Net Security (). “Hackers bury inboxes in spam then show up on Microsoft Teams posing as IT support”. Corroborates the spam, fake-support and remote-control warning pattern.
  5. ^ Microsoft Learn (). “Use Quick Assist to help users”. Support functionality, separate consent steps and advice to disconnect suspicious sessions; date is last updated.
  6. ^ Cisco Talos (). “IR trends Q3 2026: Actors impersonate IT help desks in vishing attacks as ransomware activity increases”. Independent observations of help-desk impersonation and voice calls leading to remote access.
  7. ^ The Hacker News (). “Attackers Pose as IT Support on Microsoft Teams, Abuse AD CS to Steal Company Data”. Corroborates Microsoft’s findings and identifies limits on disclosed incident details.
  8. ^ Microsoft Learn (). “Manage external meetings and chat with people and organizations using Microsoft identities”. External-domain defaults, domain restrictions and separate unmanaged-account controls; date is last updated.
  9. ^ Microsoft Security (). “Impersonating IT support: how threat actors turn a remote session into enterprise-wide access”. Earlier primary guidance on independent verification and restricting remote-support tools.
  10. ^ Microsoft Learn. “Security assessment: Certificates”. Explains insecure certificate permissions and configuration checks for ESC1 and ESC8.
  11. ^ Microsoft Support. “KB5005413: Mitigating NTLM Relay Attacks on Active Directory Certificate Services”. Official secure configuration guidance for certificate enrolment services.

Situation Room articles are updated as events develop: updates are added to the timeline, and never edited away. Follow them by email or RSS.