Hackers Pose as IT Support on Microsoft Teams to Take Remote Control of Windows PCs

Cybercriminals are posing as IT technicians on Microsoft Teams and persuading employees to hand over control of their Windows computers.

The campaign turns a familiar support conversation into a direct path for installing malware, leaving the intruder able to work on the victim’s device as if sitting in front of it.

The attack begins through external Teams contact, where an operator builds trust and asks the target to open Windows Quick Assist.

Once the user approves the session, the attacker can download and launch a harmful installer, bypassing the need to exploit a software flaw or steal a password first.

Unit 42 analysts identified the activity as a fake help-desk operation that combines social engineering, remote-control abuse and a hidden command channel.

Unit 42 said in a report shared with Cyber Security News (CSN) that the method ultimately gives operators interactive access for reconnaissance and possible follow-on theft or network intrusion. The campaign matters because it abuses tools and services many organizations already allow.

A convincing Teams message, a built-in remote assistance feature and traffic routed through cloud infrastructure can make the activity look less suspicious than a conventional malware delivery attempt, while placing a critical security decision in the hands of one employee.

Hackers Pose as IT Support on Microsoft Teams

The callers impersonate an IT technician and use Teams external access to reach targets. They direct the employee to Quick Assist, a native Windows utility intended for legitimate support, and seek approval for a remote session.

Similar Teams support call compromises show why an unexpected request for remote help must be verified through a known internal channel, not through the caller’s instructions.

After gaining control, the operator retrieves an MSI installer from an attacker-controlled Amazon S3 location and runs it with Windows Installer.

The package can use a name that resembles a routine update, then places a legitimate signed application alongside a harmful supporting file. This approach is part of a wider pattern of malware delivery through Teams, where trusted workplace platforms are used to lower a victim’s guard.

When the legitimate program opens, it loads the nearby malicious DLL rather than the normal Windows copy. Known as DLL sideloading, this lets the harmful code operate under the appearance of a signed application.

The DLL makes an encrypted connection to an AWS API Gateway endpoint, an example of how attackers can hide command traffic within ordinary cloud service activity.

Hidden Shell Evades Detection

The sideloaded DLL does not itself provide the attacker with the final command prompt. Instead, it uses Windows Management Instrumentation, or WMI, to start a separate reverse-shell program.

That separation weakens simple process-tree checks because the malicious shell is not launched directly by the signed loader, a tactic also seen in recent DLL sideloading campaigns.

The shell listens only on the infected computer’s local address and exchanges data with the DLL, which retains the outside connection.

It then opens a hidden command prompt that attackers use to check the logged-in user, network settings, domain accounts and device registration.

The group can also inspect cloud-synced document folders, creating an immediate risk to business data and identity information.

Defenders should restrict or closely monitor Teams contact from untrusted external accounts, and make clear that IT staff will not request Quick Assist access through unsolicited chats or calls.

Organizations should review whether Quick Assist is necessary, train employees to independently confirm support requests, and investigate unusual remote sessions promptly.

Guidance from Microsoft Teams vishing attacks reinforces that a request to start remote-support software deserves the same caution as a suspicious attachment.

Security teams should watch for signed applications loading unsigned DLLs from their own folders, unexpected WMI-spawned processes and unusual local listeners.

They should also examine outbound encrypted connections from trusted programs to execute-api endpoints, especially where a child process begins system discovery.

Correlating those signs with recent external Teams contact and Quick Assist activity can expose the operation during early stages of the compromise.

Indicators of Compromise (IoCs):-

Note: IP addresses and domains are intentionally defanged (e.g., [.]) to prevent accidental resolution or hyperlinking. Re-fang only within controlled threat intelligence platforms such as MISP, VirusTotal, or your SIEM.

Prevent incidents due to slow investigations. Power your Tier 1 with threat intelligence from 15K SOCs: Integrate TI Lookup in your SOC

The post Hackers Pose as IT Support on Microsoft Teams to Take Remote Control of Windows PCs appeared first on Cyber Security News.