Arctic Wolf Details Teams External-Chat Social Engineering and Payload Chain

Summary
Arctic Wolf analyzed 400+ incidents of attackers abusing Teams external chat for impersonation and initial access. It details a PowerShell-based payload chain and recommends restricting external access and monitoring chat and endpoint activity.
Key points
- Arctic Wolf analyzed more than 400 incidents involving abuse of Microsoft Teams external chat for social engineering and initial access; the activity abuses a legitimate feature, not a known Teams vulnerability.
- Attackers impersonated IT support using external tenants and convincing display names. Some cases involved email bombing followed by Teams outreach or vishing.
- Attackers commonly sought access through Quick Assist or other remote monitoring and management tools; Arctic Wolf says activity could progress from user engagement to payload execution in under 15 minutes.
- In a detailed example, a user-launched PowerShell command downloaded an MSI containing an obfuscated script and archive. The resulting implant queried Active Directory and sent information to C2 endpoints.
- Arctic Wolf identifies the Teams ChatCreated event as an opportunity to detect suspicious first contact before a user engages, and recommends correlating it with email, identity, and endpoint telemetry.
- Recommended defenses include limiting external Teams access to trusted organizations, blocking trial tenants and unmanaged accounts, restricting unauthorized remote-access tools, and verifying support requests through a separate trusted channel.
Article Details
- Attack Vectors
- Attackers used external Microsoft Teams one-to-one chats from newly created or acquired tenants to impersonate internal IT support.
- In some reported cases, an inbox flood of newsletter or subscription confirmations preceded the Teams contact, creating urgency and obscuring legitimate email.
- Attackers used Teams voice calls (vishing) to persuade victims to install or run remote-access software, including Quick Assist and other RMM tools.
- In an observed infection chain, the attacker instructed a victim to run a PowerShell command and launch a downloaded file. PowerShell retrieved an MSI from Azure Blob Storage; the MSI dropped and executed an obfuscated PowerShell script that decrypted and ran a loader, which extracted a Python interpreter and implant from a bundled ZIP archive.
- The implant queried Active Directory for computer and user objects and sent the collected information to C2 endpoints selected from domains and URIs embedded in its code.
- Defensive Notes
- Restrict Teams external access to an allow-list of trusted organizations; block unmanaged or consumer accounts and federation with trial-only tenants where appropriate.
- Monitor Teams ChatCreated events, especially chats from unfamiliar tenants or contacts using IT-support names, and correlate them with email-bombing, endpoint, identity, domain, and remote-access telemetry.
- Restrict Quick Assist to authorized IT roles and block or remove unsanctioned RMM tools; alert on unauthorized RMM execution and investigate follow-on reconnaissance.
- Require out-of-band verification for remote-access requests, such as a callback to a registered number or approval through a separate trusted application.
- Train staff to verify the External label and sender domain, treat unsolicited IT-support chats as suspicious, and retain first-contact and Safe Links warnings.
Indicators of compromise
| Type | Indicator | Context |
|---|---|---|
| DOMAIN | fix-it[.]top | Named as a cheap disposable .top domain used in the reported payload-staging and C2 infrastructure shift. |
| DOMAIN | get-help-systems[.]top | Named as a cheap disposable .top domain used in the reported payload-staging and C2 infrastructure shift. |
| DOMAIN | getitconnect[.]top | Named as a cheap disposable .top domain used in the reported payload-staging and C2 infrastructure shift. |
| DOMAIN | getsysmonitor[.]top | Listed as attacker infrastructure themed as an update domain for payload and C2 activity. |
| DOMAIN | ggc[.]com[.]ph | Listed among repeatedly observed payload or credential-phishing domains. |
| DOMAIN | help-desk-get[.]top | Named as a cheap disposable .top domain used in the reported payload-staging and C2 infrastructure shift. |
| DOMAIN | helpdesk-call[.]com | Listed as a help-desk lookalike domain used as impersonation infrastructure. |
| DOMAIN | helpdesk-s1x[.]com | Listed as a help-desk lookalike domain used as impersonation infrastructure. |
| DOMAIN | helpdesk-support-office-3[.]com | Listed as a help-desk lookalike domain used as impersonation infrastructure. |
| DOMAIN | helpdesk-support-office-4[.]com | Listed as a help-desk lookalike domain used as impersonation infrastructure. |
| DOMAIN | helpdesk-support-us-ny[.]com | Listed as a help-desk lookalike domain used as impersonation infrastructure. |
| DOMAIN | helpdesk-support-us3[.]com | Listed as a help-desk lookalike domain used as impersonation infrastructure. |
| DOMAIN | helpdesk-sys[.]top | Named as a cheap disposable .top domain used in the reported payload-staging and C2 infrastructure shift. |
| DOMAIN | helpdeskteam365[.]onmicrosoft[.]com | Fake attacker tenant domain observed across intrusions and used to establish an external Teams identity. |
| DOMAIN | infoupdate-it[.]top | Listed as attacker infrastructure themed as an update domain for payload and C2 activity. |
| DOMAIN | it-seccontrol[.]top | Listed as attacker infrastructure themed as an IT/security domain for payload and C2 activity. |
| DOMAIN | itcoreportal[.]onmicrosoft[.]com | Fake attacker tenant domain observed across intrusions and used to establish an external Teams identity. |
| DOMAIN | itdeskassist[.]com | Listed as a help-desk lookalike domain used as impersonation infrastructure. |
| DOMAIN | itendpoint365[.]onmicrosoft[.]com | Fake attacker tenant domain observed across intrusions and used to establish an external Teams identity. |
| DOMAIN | kilan[.]com[.]pl | Listed among repeatedly observed payload or credential-phishing domains. |
| DOMAIN | networkadmin797[.]onmicrosoft[.]com | Fake attacker tenant domain observed across intrusions and used to establish an external Teams identity. |
| DOMAIN | programupdate-assis[.]top | Listed as attacker infrastructure themed as an update domain for payload and C2 activity. |
| DOMAIN | saludcentro[.]gov[.]co | Listed among repeatedly observed payload or credential-phishing domains. |
| DOMAIN | scapini[.]com[.]br | Listed among repeatedly observed payload or credential-phishing domains. |
| DOMAIN | sec-check-it[.]top | Listed as attacker infrastructure themed as an update domain for payload and C2 activity. |
| DOMAIN | supportedge33[.]onmicrosoft[.]com | Fake attacker tenant domain observed across intrusions and used to establish an external Teams identity. |
| DOMAIN | supportedge39[.]onmicrosoft[.]com | Fake attacker tenant domain observed across intrusions and used to establish an external Teams identity. |
| DOMAIN | sys-update-check[.]top | Listed as attacker infrastructure themed as an update domain for payload and C2 activity. |
| DOMAIN | techrelay[.]top | Listed as attacker infrastructure for payload and C2 activity. |
| DOMAIN | update-software[.]top | Listed as attacker infrastructure themed as an update domain for payload and C2 activity. |
MITRE ATT&CK
T1027 · Obfuscated Files or InformationThe article describes an obfuscated PowerShell decryption-and-execution stub containing a large hexadecimal array and encrypted data.T1036 · MasqueradingAttacker display names, lure domains, and files were styled to resemble legitimate IT or support resources.T1059.001 · PowerShellPowerShell retrieved the MSI and executed the dropped script, which decrypted and ran additional PowerShell code.T1105 · Ingress Tool TransferThe observed chain downloaded an MSI from Azure Blob Storage, which contained a script and ZIP archive with follow-on payloads.T1140 · Deobfuscate/Decode Files or InformationThe dropped PowerShell script joined and decoded a hexadecimal array, then decrypted embedded data before executing the resulting code.T1199 · Trusted RelationshipAttackers abused default-on Teams external access and cross-tenant federation to reach employees.T1204.002 · Malicious FileIn the observed infection chain, a victim was instructed to run a PowerShell command and launch the downloaded file.T1219 · Remote Access ToolsAttackers persuaded victims to use Quick Assist and other RMM software to provide remote access.T1566.003 · Spearphishing via ServiceAttackers initiated contact through one-to-one external Teams chats from unknown tenants.T1566.004 · Spearphishing VoiceAttackers used Teams voice calls and help-desk callback pretexts to persuade victims to grant remote access.T1583.001 · DomainsThe report identifies disposable .top domains used for payload staging and C2, including domains listed in the article's infrastructure examples.T1585.002 · Email AccountsThe article's ATT&CK mapping says attacker-created sender mailboxes were used to initiate contact.T1585.003 · Cloud AccountsAttackers established external Teams identities using newly created or acquired Microsoft 365 tenants, including default onmicrosoft.com tenants.T1656 · ImpersonationAttackers used IT-support display names and internal-looking labels to impersonate employees' help desks.T1667 · Email BombingIn some cases, attackers flooded victims' inboxes with subscription confirmations shortly before the Teams help-desk outreach.
Threat Actors
Malware
DarkGatewhich used the now-familiar chain of email bombing → external Teams “help desk” → Quick Assist → QakBot/DarkGate/Cobalt Strike → ransomware.GoGRPCEarlier this year, Zscaler reported on the GoGRPC campaign, in which Teams vishing and Quick Assist were used to deploy the GoGRPC backdoor.Qakbotwhich used the now-familiar chain of email bombing → external Teams “help desk” → Quick Assist → QakBot/DarkGate/Cobalt Strike → ransomware.
Vendors
Arctic WolfArctic Wolf Labs has observed a recurring social engineering pattern in hundreds of cases where threat actors have used Microsoft Teams’ external chat creation feature for impersonation scams, or to deliver maliciousMicrosofthas observed a recurring social engineering pattern in hundreds of cases where threat actors have used Microsoft Teams’ external chat creation feature for impersonation scams, or to deliver malicious files.
Products
Microsoft 365 Apps for EnterpriseTeams ships with external access (federation) turned on by default, meaning any Teams user in another Microsoft 365 tenant can find, chat with, and call an organization’s employees, provided both tenants allow externalMicrosoft Teamsobserved a recurring social engineering pattern in hundreds of cases where threat actors have used Microsoft Teams’ external chat creation feature for impersonation scams, or to deliver malicious files.Microsoft WindowsThis may be because it is built into Windows, signed by Microsoft, requires no installation, and only requires the victim to read back a six-digit code.
Tools
AnyDeskThe most commonly observed RMM tools used in relation to this scam were Quick Assist (QuickAssist.exe / msra.exe), AnyDesk, ScreenConnect (ConnectWise), TeamViewer, Atera, Zoho Assist, NetSupport, and LogMeIn.AteraThe most commonly observed RMM tools used in relation to this scam were Quick Assist (QuickAssist.exe / msra.exe), AnyDesk, ScreenConnect (ConnectWise), TeamViewer, Atera, Zoho Assist, NetSupport, and LogMeIn.Cobalt Strikethe now-familiar chain of email bombing → external Teams “help desk” → Quick Assist → QakBot/DarkGate/Cobalt Strike → ransomware.LevelWe also observed a recent shift toward paid top-level domains (TLDs) for tenant creation.LogMeInThe most commonly observed RMM tools used in relation to this scam were Quick Assist (QuickAssist.exe / msra.exe), AnyDesk, ScreenConnect (ConnectWise), TeamViewer, Atera, Zoho Assist, NetSupport, and LogMeIn.NetSupportThe most commonly observed RMM tools used in relation to this scam were Quick Assist (QuickAssist.exe / msra.exe), AnyDesk, ScreenConnect (ConnectWise), TeamViewer, Atera, Zoho Assist, NetSupport, and LogMeIn.Quick AssistThe most commonly observed RMM tools used in relation to this scam were Quick Assist (QuickAssist.exe / msra.exe), AnyDesk, ScreenConnect (ConnectWise), TeamViewer, Atera, Zoho Assist, NetSupport, and LogMeIn.ScreenConnectThe most commonly observed RMM tools used in relation to this scam were Quick Assist (QuickAssist.exe / msra.exe), AnyDesk, ScreenConnect (ConnectWise), TeamViewer, Atera, Zoho Assist, NetSupport, and LogMeIn.Splashtopand block or uninstall unsanctioned RMM tools (AnyDesk, TeamViewer, ScreenConnect, Atera, Level, Splashtop) via Defender for Endpoint or application control.TeamViewerThe most commonly observed RMM tools used in relation to this scam were Quick Assist (QuickAssist.exe / msra.exe), AnyDesk, ScreenConnect (ConnectWise), TeamViewer, Atera, Zoho Assist, NetSupport, and LogMeIn.Zoho AssistThe most commonly observed RMM tools used in relation to this scam were Quick Assist (QuickAssist.exe / msra.exe), AnyDesk, ScreenConnect (ConnectWise), TeamViewer, Atera, Zoho Assist, NetSupport, and LogMeIn.
