Fake Help Desk Calls On Teams Lead To Certificate Abuse And Data Theft

Teams help desk attack support worker headset

Attackers meanwhile posing as IT help desk staff on Microsoft Teams talked employees into handing over remote control of their work computers. SC Media reports the intrusions via The Hacker News, drawing on a Microsoft investigation. Teams help desk attack operators then abused Active Directory Certificate Services to mint login certificates for privileged accounts. One intrusion, however, ended with company data copied to an external server.

Both intrusions for example began with Teams messages and calls from outside tenants with support themed names. Display names sounded like internal support teams, so contacts looked familiar at a glance. Victims opened Quick Assist, the remote help tool built into Windows, and read the connection code back to the caller. That single code gave attackers live control of the workstation. Attackers have abused trusted channels before, while the Chrome extension hijacking cases show how far hijacked software can reach.

Inside the machine, attackers meanwhile dropped an archive into the Downloads folder and unpacked it into a folder made to resemble a Windows update. Portable Python, Bun, or Java runtimes launched the payload without a normal install. The method relied on trust and legitimate tools, not a Teams flaw. Investigators meanwhile stress that Teams itself carried no vulnerability in these cases.

Teams help desk attack support team office
Support workers wear headsets and work at desks in a bright office. (Photo: Intercity)

Active Directory Certificate Services issues the certificates users and computers present at login in the Teams help desk attack. Poorly configured templates let holders sign in as the account each certificate names. In the opening intrusion, attackers for example exploited an ESC1 template weakness to request certificates for privileged accounts. Reports list certificates for three highly privileged accounts in an opening wave, then eight more after a wider push against 16 users.

Defender automation limited the damage in that intrusion by restricting affected identities, cutting sessions, and blocking later access attempts. Logs as a result show more than 1000 blocked SMB file access attempts after containment. They still performed DCSync against a domain controller, a technique that mimics replication to pull credential data. Containment slowed the attack, yet the opening foothold already gave attackers deep access.

The second intrusion took a different route, since the ESC1 template weakness was absent in that environment. PetitPotam forced a domain controller to authenticate to a machine they controlled in the Teams help desk attack. That NTLM login reached the AD CS web enrollment page through an ESC8 relay, with no password needed. They meanwhile requested a certificate for the domain controller itself and turned a relayed login into lasting identity through Kerberos. A Chainalysis breach exposed customer names and emails after AI agents breached its systems, which shows how incident reports now read.

Defender raised ESC8 alerts in the second case, and the customer isolated the workstation before further activity followed. Investigators did not attribute either intrusion to a named group, and Microsoft gave no dates for the incidents. Researchers named the ESC1 and ESC8 weaknesses in 2021, and PetitPotam surfaced the same year. Old configuration flaws for example still open modern doors when teams leave them unpatched by policy.

Teams help desk attack colleague help screens
In an office, a support worker helps a colleague at a desk with two screens. (Photo: Jackson College)

No patch exists for these intrusions, since configuration weakness rather than a software bug drives the abuse. Guidance advises teams to verify support requests through internal channels before granting remote access. Admins meanwhile should disable unnecessary enrollment rights and tighten certificate template permissions. Extended Protection for Authentication on web enrollment adds a strong guard against relay attacks in the Teams attack.

Employees need a simple rule for support calls, and that rule starts with doubt. Real help desk staff will accept verification through an internal channel. Workers for example should hang up and call back through a known number when a request feels rushed or odd. Microsoft Teams phishing detection tackles a different scam pattern, however human caution remains the opening defence in both stories.

IT leaders should audit certificate templates, enrollment rights, and web enrollment exposure as a single exercise. Identity posture checks flag templates and endpoints exposed to ESC1 and ESC8. Windows 11 updates and Chrome extension hijacking both show how routine hygiene limits damage when attackers find a foothold.

Kind voices on support calls can open more doors than any exploit, and that truth should humble every security team. Teams help desk attack cases prove that trust needs a check, not just a password. Verify the caller, lock down certificate templates, and guard remote access with care. People protect companies best when doubt feels welcome and verification feels normal.

Stay Connected with The MES Times

Get the latest tech, AI and gadget news and updates wherever you prefer.

Follow on Google Discover

Add The MES Times to Preferred Sources and see more of our stories in Google Search and Top Stories.

Hardware Editor

Fatima Khan is a tech journalist at The MES Times, specializing in PC hardware, GPU market trends, and consumer tech developments. With a hands-on background in desktop building and hardware benchmarking, she closely tracks silicon launches from NVIDIA, AMD, and Intel, along with shifting Steam hardware metrics. Her reporting prioritizes real-world gaming performance, thermals, and price-to-value analysis for PC builders. Catch her daily updates on X @barirahayat.

0 comments Oldest comments first