Skip to navigation

Threat reportPhishingTL-2026-2302

Impersonating IT Support: Threat Actors Turn Remote Sessions into Enterprise-Wide Access via Microsoft Teams

highACTIVE

Microsoft Threat Intelligence documents a human-operated intrusion campaign in which operators impersonate IT/helpdesk staff over external Microsoft Teams chats and vishing calls to socially engineer users into granting remote access via Quick Assist, then deploy Azure-Blob-Storage-hosted MSI packages bundling a portable Node.js runtime and an obfuscated JavaScript implant (detected as SynkLoader/EtherRatz) for persistence, before moving laterally via WinRM/ADSI toward domain controllers and certificate authorities.

Key facts

IdentifiersTL-2026-2302
SeverityHIGH
Affected productsMicrosoft Microsoft Teams (external/cross-tenant chat and calling); Microsoft Quick Assist; Microsoft Windows Server Active Directory Domain Services; Microsoft Active Directory Certificate Services (AD CS)
MalwareEtherRatz, FakeAll, PowExec, SynkLoader
ToolsDormant Ethereum smart contract C2 discovery mechanism, Microsoft Quick Assist, Node.js (portable runtime), Quick Assist
MITRE ATT&CK techniquesT1018 Remote System Discovery, T1021.006 Windows Remote Management, T1036.005 Match Legitimate Resource Name or Location, T1059.001 PowerShell, T1059.007 JavaScript, T1071.001 Web Protocols, T1087.002 Domain Account, T1113 Screen Capture, T1218.007 Msiexec, T1218.011 Rundll32, T1497.001 System Checks, T1547.001 Registry Run Keys / Startup Folder and 1 more in the attack flow
MotivationFINANCIAL
Target sectorsenterprise broad cross-sector -- no specific vertical disclosed
Detection rules9 (1 shown free)
Sources8 cited sources

Detection coverage

As of 2026-09-02, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2302 across Splunk SPL, Microsoft KQL and Sigma, covering 25 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: EdgeUpdate Persistence, Renamed Node.js Execution from LocalAppData, and Post-Compromise Recon

Detects the post-exploitation cluster from this campaign: creation of the 'EdgeUpdate' HKCU Run-key persistence entry, execution of a renamed/portable Node.js interpreter out of %LocalAppData% (the JavaScript SynkLoader/EtherRatz implant loader), antivirus discovery via the SecurityCenter2 WMI namespace, and host/domain reconnaissance (systeminfo, net user /domain).

Splunk SPL

index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational"
( (EventCode=13 TargetObject="*\\CurrentVersion\\Run\\EdgeUpdate") 
  OR (EventCode=1 Image="*\\node*.exe" CommandLine="*\\AppData\\Local\\*" ParentImage!="*\\node*")
  OR (EventCode=1 (CommandLine="*net user*/domain*" OR CommandLine="*net.exe user*/domain*"))
  OR (EventCode=1 CommandLine="*systeminfo*")
  OR (EventCode=1 CommandLine="*SecurityCenter2*" (Image="*\\wmic.exe" OR Image="*\\powershell.exe" OR Image="*\\WmiPrvSE.exe")) )
| eval detection_reason=case(
    EventCode=13 AND match(TargetObject, "EdgeUpdate"), "EdgeUpdate HKCU Run-key persistence write",
    EventCode=1 AND match(Image, "(?i)node.*\.exe"), "Renamed/portable Node.js execution from LocalAppData",
    match(CommandLine, "(?i)net(\.exe)? user.*\/domain"), "Domain account discovery (net user /domain)",
    match(CommandLine, "(?i)systeminfo"), "Host reconnaissance (systeminfo)",
    match(CommandLine, "(?i)SecurityCenter2"), "AV/security-product discovery via SecurityCenter2 WMI namespace",
    true(), "other")
| table _time ComputerName User EventCode Image TargetObject CommandLine detection_reason
| sort - _time

Microsoft KQL

let RegPersist = DeviceRegistryEvents
| where Timestamp > ago(24h)
| where RegistryKey has @"CurrentVersion\Run" and RegistryValueName =~ "EdgeUpdate"
| project TimeGenerated=Timestamp, DeviceName, AccountName=InitiatingProcessAccountName, Signal="EdgeUpdate HKCU Run-key persistence write", Detail=tostring(RegistryValueData);
let NodeExec = DeviceProcessEvents
| where Timestamp > ago(24h)
| where FolderPath has @"\AppData\Local\" and FileName matches regex @"(?i)node.*\.exe"
| project TimeGenerated=Timestamp, DeviceName, AccountName, Signal="Renamed/portable Node.js execution from LocalAppData", Detail=ProcessCommandLine;
let Recon = DeviceProcessEvents
| where Timestamp > ago(24h)
| where ProcessCommandLine has_any ("net user", "systeminfo", "SecurityCenter2") and (ProcessCommandLine has "/domain" or ProcessCommandLine has "systeminfo" or ProcessCommandLine has "SecurityCenter2")
| project TimeGenerated=Timestamp, DeviceName, AccountName, Signal="Post-compromise recon (domain account / host / AV discovery)", Detail=ProcessCommandLine;
RegPersist
| union NodeExec
| union Recon
| sort by TimeGenerated desc

Sigma

title: EdgeUpdate HKCU Persistence with Renamed Node.js Loader and Post-Compromise Recon
id: 9d3f6b18-4c72-4e0a-8b1d-5a6e2f9c3d02
status: experimental
description: Detects the SynkLoader/EtherRatz post-exploitation cluster - EdgeUpdate HKCU Run-key persistence, a renamed/portable Node.js interpreter executing from %LocalAppData%, and post-compromise reconnaissance (systeminfo, net user /domain, SecurityCenter2 WMI AV discovery).
references:
    - https://www.microsoft.com/en-us/security/blog/2026/09/02/impersonating-it-support-threat-actors-turn-remote-session-into-enterprise-wide-access/
author: Threadlinqs Team
date: 2026-09-03
tags:
    - attack.persistence
    - attack.t1547.001
    - attack.defense-evasion
    - attack.t1497.001
    - attack.t1036.005
    - attack.discovery
    - attack.t1087.002
    - attack.t1018
    - attack.execution
    - attack.t1059.007
logsource:
    category: registry_event
    product: windows
detection:
    selection_persist:
        TargetObject|contains: 'CurrentVersion\Run'
        TargetObject|endswith: '\EdgeUpdate'
    selection_node:
        Image|contains|all:
            - 'node'
            - '\AppData\Local\'
    selection_recon:
        CommandLine|contains:
            - 'net user'
            - 'systeminfo'
            - 'SecurityCenter2'
    condition: 1 of selection_*
falsepositives:
    - Legitimate Microsoft Edge/WebView2 updater components (verify the actual binary path and signature - genuine EdgeUpdate lives under Program Files, not a per-user random LocalAppData folder)
    - IT/helpdesk-run diagnostic scripts that legitimately call systeminfo or net user /domain
level: high

Known false positives:

  • Legitimate Microsoft Edge/WebView2 updater components — verify the actual binary path and code-signing (genuine EdgeUpdate lives under Program Files, not a per-user random LocalAppData folder)
  • IT/helpdesk-run diagnostic scripts that legitimately call systeminfo or net user /domain

Tuning notes: Baseline and exclude your organization's legitimate Edge/WebView2 updater install path and hash; weight the EdgeUpdate registry write as the highest-fidelity single-event trigger (fire immediately, don't require correlation) and treat the recon commands as lower-confidence context that should raise, not solely drive, an alert.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • PowerShell Download of Decoy MSI from Teams-Impersonation Azure Blob Endpoint Followed by Silent Install · unlock with TL Creds
  • EdgeUpdate Persistence, Renamed Node.js Execution from LocalAppData, and Post-Compromise Recon · unlock with TL Creds
  • HTTPS Long-Polling Beacon to Known C2 Domains, Rundll32 Proxy Execution, and WinRM Lateral Movement · unlock with TL Creds
  • Decoy MSI Download from Teams-Impersonation Azure Blob Storage Endpoint · unlock with TL Creds
  • EdgeUpdate HKCU Persistence with Renamed Node.js Loader and Post-Compromise Recon · unlock with TL Creds
  • SynkLoader C2 Beacon, Rundll32 Proxy Execution, and WinRM Lateral Movement · unlock with TL Creds
  • PowerShell Download of Decoy MSI from Teams-Impersonation Azure Blob Endpoint Followed by Silent Install · unlock with TL Creds
  • HTTPS Long-Polling Beacon to Known C2 Domains, Rundll32 Proxy Execution, and WinRM Lateral Movement · unlock with TL Creds

Indicators of compromise

As of 2026-09-02, Threadlinqs Intelligence tracks 25 indicators of compromise for TL-2026-2302.

Sample indicators (3 of 25)

  • Domain: update1n5[.]blob[.]core[.]windows[.]net
  • File hash: 4cfdcae6dd1d6d98b870c8f0654d504f2bf10479a117dc297de789c249dc389d
  • Domain: update1n6[.]blob[.]core[.]windows[.]net

Defanged, TLP:CLEAR. Full set of 25 indicators: unlock with TL Creds.

25 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

Microsoft Threat Intelligence's September 2, 2026 report details a campaign in which an external-tenant operator initiates a Microsoft Teams chat or call while impersonating IT/helpdesk staff, using pretexts such as 'Microsoft Security Update,' 'Spam Filter Update,' and 'Account Verification' (occasionally reinforced with voice phishing) to persuade the victim to override external-contact security warnings. Once trust is established, the operator talks the victim into launching Windows Quick Assist (or a generic RMM tool) and granting an interactive remote session.

With hands-on-keyboard access, the operator uses PowerShell to download an MSI package -- disguised under decoy names such as 'devfix' or 'Hotfix' -- from a set of dedicated Azure Blob Storage endpoints (update1n5/6/7/9.blob.core.windows.net and updatetmp.blob.core.windows.net) and installs it silently via `msiexec /qn`. The MSI bundles a legitimate, portable Node.js runtime that is extracted (and its executable renamed for evasion) into a randomly named directory under %LocalAppData%, plus an obfuscated JavaScript implant. A staged loader decrypts the implant in-memory or to temporary files carrying nonstandard extensions (.tmp, .ini, .dat, .bin, .cfg) to blend in with legitimate application data. Microsoft Defender detects components of this toolset as Trojan:JS/SynkLoader.SA, Trojan:Win32/SynkLoader.SA, Trojan:JS/EtherRatz.A!MTB, Trojan:JS/EtherRatz.B!MTB, Trojan:PowerShell/PowExec.MX!MTB, and the Trojan:Win32|JS/FakeAll family.

Persistence is established per-user during MSI installation via an HKEY_CURRENT_USER \...\Run registry entry named 'EdgeUpdate' and a Startup-folder shortcut that launches WScript, both of which re-invoke the Node.js loader from LocalAppData on logon. The implant communicates over randomized HTTPS long-polling to a small set of C2 domains -- a hardcoded fallback at synctimes.australiaeast.cloudapp.azure.com, a primary channel at webwether.eastus.cloudapp.azure.com, and dssdfvsdfvsdfvsdgbfbdvdzv.org -- and recovered samples contain a dormant blockchain-based discovery capability (monitoring an Ethereum smart contract for updated C2 URLs) that was disabled at analysis time. Before further action, the implant performs defense-evasion and reconnaissance checks: virtual-adapter detection, antivirus discovery via the SecurityCenter2 WMI namespace, `systeminfo`, and `net user /domain`, and exfiltrates base64-encoded desktop screenshots via PowerShell.

For follow-on access, the operator uses rundll32.exe to proxy-execute threat-actor-supplied DLLs, then pivots laterally by exploiting WinRM (TCP 5985) and issuing ADSI queries to enumerate domain accounts, servers, and user descriptions, deliberately working toward domain controllers, certificate authorities, file servers, and database/application servers. Microsoft assesses this pattern as 'especially high-impact' because it hands the operator credential-backed, interactive access to core identity and PKI infrastructure, with realistic follow-on risk of data theft, extortion, or ransomware deployment.

No CVE or software vulnerability underlies this campaign -- it is a technique/tooling-based human-operated intrusion. The September blog explicitly extends a foundational playbook Microsoft published on April 18, 2026 ('Cross-tenant helpdesk impersonation to data exfiltration'), which documented the same Teams-impersonation-to-Quick-Assist/AnyDesk/TeamViewer pattern with WinRM lateral movement, DLL side-loading, and Rclone-based exfiltration, and traces back to the Quick-Assist-abuse technique Microsoft first documented in May 2024 in connection with the financially motivated cluster Storm-1811 (Black Basta ransomware). Independent researchers separately tracked a related but infrastructurally distinct SynkLoader campaign from late July/August 2026 (Python/PowerShell/C#/C++ multi-module toolkit with a fake Windows 11 lock-screen credential harvester, RAT, and VNC module, delivered via a 'PowerShell Cleaner' MSI, using different Azure-hosted infrastructure and C2 domains than the Node.js/JavaScript variant Microsoft describes here), underscoring that Teams helpdesk impersonation has become a shared initial-access technique used by multiple financially motivated operators -- alongside separately tracked clusters such as UNC6692 -- rather than the signature of a single named actor. Microsoft's report itself makes no formal threat-actor attribution or Storm-#### assignment for this specific variant.

MITRE ATT&CK techniques by tactic:

Discovery

T1018 Remote System Discovery; T1087.002 Domain Account

Lateral Movement

T1021.006 Windows Remote Management

Defense Evasion

T1036.005 Match Legitimate Resource Name or Location; T1218.007 Msiexec; T1218.011 Rundll32; T1497.001 System Checks

Execution

T1059.001 PowerShell; T1059.007 JavaScript

Command and Control

T1071.001 Web Protocols

Collection

T1113 Screen Capture

Persistence

T1547.001 Registry Run Keys / Startup Folder

Initial Access

T1566.003 Spearphishing via Service

Remediation

Immediate actions

  • Restrict Microsoft Teams external/federated chat to an explicit allow-list of trusted tenants and block unsolicited contact from unknown organizations
  • Alert on and quarantine external Teams chats/calls impersonating IT or helpdesk personnel (e.g., display names 'Help Desk', 'Help Desk IT', 'IT Support')
  • Restrict end-user launch of Quick Assist and other remote-access utilities unless tied to a verified internal support ticket
  • Block or allow-list execution of MSI packages downloaded via PowerShell from Azure Blob Storage endpoints not on an approved corporate list

Workarounds

  • Require a verified ticket number plus independent callback validation before granting any remote-access session solicited via chat or phone
  • Disable Quick Assist via policy for users who do not have a legitimate business need for it

Longer-term hardening

  • Deploy EDR/behavioral detection for portable or renamed Node.js interpreters executing staged payloads from user-writable paths (%LocalAppData%, %Temp%, %AppData%)
  • Monitor and alert on WinRM (TCP 5985) session initiation from non-administrative source processes and on anomalous ADSI/LDAP enumeration of domain accounts and servers
  • Implement Attack Surface Reduction rules blocking script-based payload staging and living-off-the-land binary proxy execution (msiexec.exe, rundll32.exe)
  • Enforce tiered administration and network segmentation so a standard endpoint compromise cannot directly reach domain controllers or certificate authorities
  • Hunt for the 'EdgeUpdate' HKCU Run-key persistence pattern and matching Startup-folder WScript shortcuts across the fleet

Affected and fixed versions

  • Microsoft — Microsoft Teams (external/cross-tenant chat and calling)
    Vulnerable versions: N/A -- abuses default external-contact functionality, not a code vulnerability
    Fixed in: N/A
  • Microsoft — Quick Assist
    Vulnerable versions: All versions (feature/trust abuse, not a vulnerability)
    Fixed in: N/A
  • Microsoft — Windows Server Active Directory Domain Services
    Vulnerable versions: All supported versions -- targeted post-compromise via WinRM/ADSI lateral movement
    Fixed in: N/A
  • Microsoft — Active Directory Certificate Services (AD CS)
    Vulnerable versions: All supported versions -- targeted post-compromise for PKI/certificate authority access
    Fixed in: N/A

Timeline

  • Microsoft first documents threat actors abusing Quick Assist in social-engineering attacks leading to ransomware, attributed to the financially motivated cluster Storm-1811 -- establishing the helpdesk-impersonation-to-remote-access technique this campaign builds on.
  • Microsoft publishes the 'Cross-tenant helpdesk impersonation to data exfiltration' human-operated intrusion playbook, documenting Teams-based IT impersonation combined with Quick Assist/AnyDesk/TeamViewer, WinRM lateral movement, DLL side-loading, and Rclone exfiltration.
  • Independent researchers date the compilation of the first SynkLoader malware samples distributed via Microsoft Teams 'PowerShell Cleaner' MSI lures impersonating IT support.
  • Avertium and other independent researchers publish analysis of the SynkLoader malware family's multi-module architecture (fake lock-screen credential harvester, RAT, VNC module) delivered through Microsoft Teams IT-support impersonation.
  • Microsoft characterizes the intrusion pattern as 'especially high-impact' given the credential-backed interactive access it grants to internal infrastructure, warning of realistic follow-on data theft, extortion, or ransomware deployment.
  • Microsoft Threat Intelligence publishes 'Impersonating IT support' documenting a Node.js/JavaScript-implant variant of the campaign: disguised MSI packages hosted on dedicated Azure Blob Storage endpoints, EdgeUpdate registry/startup persistence, and WinRM/ADSI-driven lateral movement toward domain controllers and certificate authorities.

Sources cited

Previous and next in phishing

Drafted by the Threadlinqs research pipeline from 8 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats