Threat Summary
AlienVault OTX pulse activity modified 2026-09-02 highlights a social-engineering campaign in which attackers weaponize Microsoft Teams help-desk calls to convince users to run tooling, grant remote access, or execute first-stage payloads, followed by lateral movement inside the network. The pulse is TLP:WHITE, actor attribution is unknown, malware family is not named, and MITRE mapping is not provided, so confidence is moderate and the detection focus should be behavior-first rather than family-first.
The likely chain is: Teams chat/call from an external or spoofed help-desk identity -> urgency around MFA, VPN, mailbox, or device compliance -> user is guided to launch Quick Assist, AnyDesk, TeamViewer, ScreenConnect, PowerShell, mshta, rundll32, or a browser-delivered loader -> interactive operator hands-on-keyboard activity -> credential/session theft -> SMB/RDP/WinRM or cloud-token pivot. The objective is usually initial access for follow-on intrusion: credential harvesting, email abuse, data staging, ransomware precursor access, or resale to access brokers.
Threat Actor / Malware Profile
- Attribution: Unknown in OTX; consistent with initial-access brokers and ransomware-affiliate playbooks that abuse trusted collaboration channels.
- Distribution method: Microsoft Teams inbound chat/call, fake internal help desk, external tenant contact, compromised account, or lookalike display name; user-assisted execution is the key weakness.
- Payload behavior: Frequently not a classic EXE drop. Expect legitimate signed binaries and RMM tools abused as the payload:
quickassist.exe,AnyDesk.exe,TeamViewer.exe,ScreenConnect*.exe,powershell.exe,mshta.exe,rundll32.exe,wscript.exe, or browser downloads launched from Teams/Edge. - C2 communication: OTX lists IPv4-only indicators, suggesting direct-IP RMM relays, low-reputation VPS, bulletproof hosting, or short-lived loader/C2 endpoints. Validate against DNS, TLS SNI, JA3/JA4, ASN, and passive DNS before treating as durable C2.
- Persistence mechanism: Common persistence after interactive access includes Run keys, scheduled tasks, new local admin accounts, RMM service installation, RDP enablement, firewall changes, LSA/credential tampering, and token theft rather than a single malware service.
- Anti-analysis techniques: Living-off-the-land binaries, user consent prompts, time-boxed operations, direct-IP endpoints to evade domain reputation, signed RMM binaries, cleanup of Downloads/Temp, and disabling Defender/EDR where privileges are obtained.
IOC Analysis
The pulse contains 8 IPv4 indicators and no domains, hashes, URLs, or mutexes in the sample. Treat these as network tripwires and pivot seeds, not complete coverage:
5.181.3.106178.130.47.4680.66.72.215185.155.99.16145.8.157.1852.56.172.214185.234.67.53136.0.20.6
SOC operationalization: add to firewall/proxy/DNS sinkhole and EDR network watchlists for 30 days; alert on any inbound or outbound session, especially to/from user endpoints and Teams-adjacent processes. Enrich with ASN, geolocation, passive DNS, TLS certificates, VirusTotal/OTX related pulses, NetFlow, and first-seen/last-seen. Because IPs are volatile and may be shared infrastructure, combine IP matches with process ancestry, RMM execution, help-desk impersonation telemetry, and impossible travel or MFA fatigue signals.
Detection Engineering
---
title: Microsoft Teams Help-Desk Social Engineering Leading to Suspicious Child Process
id: 9f2c0e9a-7b6f-4d20-a9db-teams-helpdesk-childproc
status: experimental
description: Detects Microsoft Teams or Edge/Teams WebView spawning script interpreters, LOLBins, or RMM tooling consistent with fake help-desk calls and user-assisted execution.
author: Security Arsenal
logsource:
category: process_creation
product: windows
service: sysmon
level: high
tags:
- attack.initial_access
- attack.t1566
- attack.t1204
- attack.t1219
- attack.t1059
detection:
parent_teams:
ParentImage|endswith:
- '\Teams.exe'
- '\ms-teams.exe'
- '\msedgewebview2.exe'
- '\explorer.exe'
child_suspicious:
Image|endswith:
- '\powershell.exe'
- '\pwsh.exe'
- '\mshta.exe'
- '\rundll32.exe'
- '\wscript.exe'
- '\cscript.exe'
- '\cmd.exe'
- '\quickassist.exe'
- '\AnyDesk.exe'
- '\TeamViewer.exe'
- '\ScreenConnect.Client.exe'
- '\ScreenConnect.WindowsClient.exe'
cmdline_suspicious:
CommandLine|contains:
- 'http://'
- 'https://'
- 'iex'
- 'Invoke-Expression'
- 'DownloadString'
- 'FromBase64String'
- '-enc'
- '-e '
- 'bypass'
- 'hidden'
- 'msiexec'
- 'certutil'
- 'bitsadmin'
condition: parent_teams and child_suspicious and cmdline_suspicious
falsepositives:
- Legitimate help desk using approved RMM with change ticket
- IT support scripts launched after verified callback
references:
- https://cybersecuritynews.com/hackers-weaponize-microsoft-teams/
date: 2026/09/04
modified: 2026/09/04
---
title: OTX Pulse IPv4 Network Indicators - Teams Help-Desk Intrusion Set
id: 4a2fd0d9-6b1f-42f0-a4b1-otx-teams-ipv4-watch
status: experimental
description: Network connection to OTX-listed IPv4 indicators associated with Teams help-desk social engineering and lateral movement. Deploy at firewall, proxy, DNS resolver, Zeek/Suricata, or EDR network telemetry where supported.
author: Security Arsenal
logsource:
category: network_connection
product: windows
service: sysmon
level: critical
tags:
- attack.command_and_control
- attack.t1071
- attack.t1219
- attack.lateral_movement
detection:
dst_ip_otx:
DestinationIp:
- '5.181.3.106'
- '178.130.47.46'
- '80.66.72.215'
- '185.155.99.161'
- '45.8.157.185'
- '2.56.172.214'
- '185.234.67.53'
- '136.0.20.6'
process_interesting:
Image|endswith:
- '\Teams.exe'
- '\ms-teams.exe'
- '\powershell.exe'
- '\mshta.exe'
- '\rundll32.exe'
- '\AnyDesk.exe'
- '\TeamViewer.exe'
- '\ScreenConnect.Client.exe'
- '\mstsc.exe'
- '\winrm.cmd'
- '\wsmprovhost.exe'
condition: dst_ip_otx and process_interesting
falsepositives:
- Rare if IP reputation is validated; still suppress only approved RMM vendor ranges after ticketing.
references:
- https://cybersecuritynews.com/hackers-weaponize-microsoft-teams/
date: 2026/09/04
modified: 2026/09/04
---
title: Post-Help-Desk Intrusion Persistence via RMM Service, Run Key, or Remote Access Enablement
id: 7f1db9b7-6b95-4d5f-b2de-rmm-persistence-remoteaccess
status: experimental
description: Detects persistence or remote-access enablement shortly after user-assisted support scams: new services, Run keys, RDP enablement, local admin creation, or RMM installation paths.
author: Security Arsenal
logsource:
category: registry_event
product: windows
service: sysmon
level: high
tags:
- attack.persistence
- attack.t1543.003
- attack.t1547.001
- attack.t1136
- attack.t1021.001
- attack.t1219
detection:
reg_persistence:
TargetObject|contains:
- '\CurrentVersion\Run'
- '\CurrentVersion\RunOnce'
- '\Services\'
- '\Control\Terminal Server\fDenyTSConnections'
- '\Lsa'
- '\Winlogon'
reg_value_suspicious:
Details|contains:
- 'powershell'
- 'mshta'
- 'rundll32'
- 'AnyDesk'
- 'TeamViewer'
- 'ScreenConnect'
- 'QuickAssist'
- 'AppData\Local\Temp'
- 'ProgramData'
condition: reg_persistence and reg_value_suspicious
falsepositives:
- Managed software deployment and approved RMM inventory
- Help-desk tools installed through Intune/SCCM with approved package IDs
references:
- https://cybersecuritynews.com/hackers-weaponize-microsoft-teams/
date: 2026/09/04
modified: 2026/09/04
let OtxIps = dynamic(['5.181.3.106','178.130.47.46','80.66.72.215','185.155.99.161','45.8.157.185','2.56.172.214','185.234.67.53','136.0.20.6']);
let SuspiciousProcs = dynamic(['powershell.exe','pwsh.exe','mshta.exe','rundll32.exe','wscript.exe','cscript.exe','cmd.exe','quickassist.exe','AnyDesk.exe','TeamViewer.exe','ScreenConnect.Client.exe','ScreenConnect.WindowsClient.exe','mstsc.exe','wsmprovhost.exe']);
union withsource=src
(
DeviceNetworkEvents
| where TimeGenerated > ago(14d)
| where RemoteIP in (OtxIps)
| project src, TimeGenerated, DeviceName, DeviceId, InitiatingProcessFileName, InitiatingProcessParentFileName, InitiatingProcessCommandLine, LocalIP, LocalPort, RemoteIP, RemotePort, RemoteUrl, ActionType
),
(
DeviceProcessEvents
| where TimeGenerated > ago(14d)
| where (InitiatingProcessFileName in~ ('Teams.exe','ms-teams.exe','msedgewebview2.exe','explorer.exe') and FileName in~ (SuspiciousProcs))
or (ProcessCommandLine has_any ('iex','DownloadString','FromBase64String','-enc','bypass','hidden','AnyDesk','TeamViewer','ScreenConnect','quickassist'))
| project src, TimeGenerated, DeviceName, DeviceId, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessParentFileName, InitiatingProcessCommandLine, AccountName, AccountDomain, SHA256, FolderPath
)
| extend IndicatorMatch = iif(RemoteIP in (OtxIps), 'OTX IPv4', 'Behavior')
| summarize FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated), Hits=count(), Processes=make_set(FileName,10), Parents=make_set(InitiatingProcessFileName,10), CommandLines=make_set(strcat(substring(ProcessCommandLine,0,220)),5), RemoteEndpoints=make_set(strcat(RemoteIP,':',tostring(RemotePort)),10) by DeviceName, DeviceId, AccountName, IndicatorMatch
| order by Hits desc;
# Security Arsenal hunt: Teams help-desk vishing IOC/artifact sweep
$ErrorActionPreference = 'SilentlyContinue'
$OtxIps = @('5.181.3.106','178.130.47.46','80.66.72.215','185.155.99.161','45.8.157.185','2.56.172.214','185.234.67.53','136.0.20.6')
$RmmNames = 'AnyDesk|TeamViewer|ScreenConnect|QuickAssist|Atera|Splashtop|ZohoAssist|LogMeIn|RustDesk'
Write-Host '[*] Active/historical TCP connections to OTX IPv4 indicators'
Get-NetTCPConnection | Where-Object { $OtxIps -contains $_.RemoteAddress } | Select-Object LocalAddress,LocalPort,RemoteAddress,RemotePort,State,OwningProcess,@{n='Process';e={(Get-Process -Id $_.OwningProcess).ProcessName}},@{n='Path';e={(Get-Process -Id $_.OwningProcess).Path}}
Write-Host '[*] Listening services/processes resembling RMM or remote access'
Get-CimInstance Win32_Service | Where-Object { $_.Name -match $RmmNames -or $_.PathName -match $RmmNames -or $_.DisplayName -match $RmmNames } | Select-Object Name,DisplayName,State,StartMode,PathName
Get-Process | Where-Object { $_.ProcessName -match $RmmNames } | Select-Object ProcessName,Id,Path,StartTime
Write-Host '[*] Persistence: Run keys and scheduled tasks with suspicious command lines'
$RunKeys = @('HKLM:\Software\Microsoft\Windows\CurrentVersion\Run','HKLM:\Software\Microsoft\Windows\CurrentVersion\RunOnce','HKCU:\Software\Microsoft\Windows\CurrentVersion\Run','HKCU:\Software\Microsoft\Windows\CurrentVersion\RunOnce')
foreach ($k in $RunKeys) { Get-ItemProperty $k | ForEach-Object { $_.PSObject.Properties | Where-Object { $_.Value -match 'powershell|mshta|rundll32|AnyDesk|TeamViewer|ScreenConnect|Temp|ProgramData' } | Select-Object @{n='Key';e={$k}},Name,@{n='Value';e={$_.Value}} } }
Get-ScheduledTask | Where-Object { ($_.Actions.Execute -match 'powershell|mshta|rundll32|wscript|cscript') -or ($_.Actions.Arguments -match 'iex|DownloadString|FromBase64String|-enc|bypass|hidden|AnyDesk|TeamViewer|ScreenConnect') } | Select-Object TaskName,TaskPath,State,@{n='Execute';e={$_.Actions.Execute}},@{n='Arguments';e={$_.Actions.Arguments}}
Write-Host '[*] Remote access enablement and local admin anomalies'
Get-ItemProperty 'HKLM:\System\CurrentControlSet\Control\Terminal Server' | Select-Object fDenyTSConnections
Get-LocalGroupMember -Group 'Administrators' | Select-Object Name,PrincipalSource,ObjectClass
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon' | Select-Object AutoAdminLogon,DefaultUserName,DefaultDomainName
Write-Host '[*] Recent likely drop locations and Teams/WebView cache artifacts'
$paths = @("$env:LOCALAPPDATA\Temp","$env:APPDATA","$env:LOCALAPPDATA\Microsoft\Teams","$env:LOCALAPPDATA\Packages\MSTeams_8wekyb3d8bbwe","$env:USERPROFILE\Downloads")
foreach ($p in $paths) { Get-ChildItem $p -Recurse -ErrorAction SilentlyContinue | Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-14) -and ($_.Name -match '\.exe$|\.msi$|\.ps1$|\.js$|\.vbs$|\.hta$|\.zip$|\.iso$|\.img$|AnyDesk|TeamViewer|ScreenConnect|quickassist') } | Select-Object FullName,Length,CreationTime,LastWriteTime }
Write-Host '[*] Defender/EDR relevant tamper signals'
Get-MpPreference | Select-Object DisableRealtimeMonitoring,DisableBehaviorMonitoring,DisableIOAVProtection,DisableScriptScanning,ExclusionPath,ExclusionProcess
Get-WinEvent -LogName 'Microsoft-Windows-Windows Defender/Operational' -MaxEvents 200 | Where-Object { $_.Id -in 5001,5007,5013 } | Select-Object TimeCreated,Id,Message
Response Priorities
- Immediate: Block and alert on all eight IPv4 indicators at egress firewall, secure web gateway, DNS resolver, EDR, and mail/Teams-adjacent controls; isolate hosts with matching connections; capture memory and process tree for Teams/Edge/WebView child processes; suspend unapproved RMM executables via AppLocker/WDAC/EDR policy.
- 24h: If any credential, MFA, browser session, token, or help-desk secret may have been exposed, force password reset and revoke refresh tokens/session cookies for impacted users; review Entra ID/O365 sign-in, MFA fatigue, inbox rules, OAuth consent, Teams external access, and new device registrations; validate caller identity by callback using a directory number, never the number supplied in chat.
- 1 week: Harden collaboration identity by restricting external Teams chat/calls, requiring verified help-desk workflow, blocking user consent to unapproved remote tools, constraining Quick Assist/RMM to IT-managed packages, deploying attack surface reduction rules for Office/Teams child processes, disabling legacy auth, tightening RDP/SMB/WinRM lateral paths, and adding just-in-time admin for support staff.
Related Resources
Security Arsenal Incident Response Managed SOC & MDR Services AlertMonitor Threat Detection From The Dark Side Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.