Back to Intelligence

ScreenConnect RMM Abuse + SockTz AI-Enabled Intrusions + Teams Help Desk Vishing: OTX Pulse Analysis — Enterprise Detection Pack

SA
Security Arsenal Team
September 3, 2026
10 min read

Three concurrent OTX pulses reveal a converging trend across crimeware operators: the weaponization of trusted software and legitimate collaboration platforms as delivery and persistence mechanisms.

Pulse 1 — ScreenConnect RMM Abuse Campaign: A multi-wave social engineering operation uses lures themed around Zoom updates, business documents, and system utilities to deploy ScreenConnect Remote Monitoring and Management (RMM) agents. The attack chain employs VBScript droppers, batch loaders, compiled .NET executables, and HTML phishing pages, all staging payloads from a WsgiDAV server at 207.174.0.143:8080. Additional staging was observed at 207.189.11.170 serving C# source artifacts (working_payload.cs), suggesting operators are compiling payloads semi-dynamically. Supporting infrastructure includes the domain crestmarkhq.com and the subdomain blog.derrspecial-onlinedmin.live. The campaign exhibits deliberate Windows Defender evasion, code-signing abuse, and Cloudflare tunnel usage to mask C2 egress — a cross-platform operation with professional tradecraft.

Pulse 2 — AI-Enabled Intrusions Targeting Latin America (SockTz): Two multi-stage intrusion campaigns are hitting transportation, government, and finance organizations in Brazil, Ecuador, and Mexico. Campaign CL-CRI-1131 targeted Mexican transportation and Ecuadorian government entities using living-off-the-land (LotL) techniques and self-hosted NextChat instances — meaning operators are running private LLM frontends to generate phishing content, scripts, and tooling without vendor telemetry. The SockTz malware establishes a SOCKS5 proxy on victim machines, converting compromised hosts into traffic relays for downstream operations. C2 infrastructure relies heavily on DuckDNS dynamic DNS (m-doxa-apodo.duckdns.org, m-doxa-geo.duckdns.org, m-doxa-intel.duckdns.org, m-doxa-vacunas.duckdns.org) resolving to 167.148.195.53. The hostname naming (vacunas = vaccines, intel, geo) indicates Spanish-language lure theming aligned with government service impersonation.

Pulse 3 — Microsoft Teams Help Desk Vishing: Threat actors are impersonating internal IT help desk staff via Microsoft Teams calls and chats to socially engineer users into executing malware or granting remote access, followed by lateral movement. Eight IPv4 indicators (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) represent payload delivery and C2 staging servers, predominantly on low-reputation hosting ranges.

Collective assessment: All three pulses share a doctrine — abuse trust (RMM tools, Teams identity, AI-generated lures) rather than exploit vulnerabilities. Objectives span initial access brokering, SOCKS5 proxy monetization, and lateral movement staging consistent with pre-ransomware positioning.

Threat Actor / Malware Profile

ScreenConnect RMM Abuse Cluster (Unattributed)

  • Distribution: Phishing with Zoom-update and business-document lures; HTML phishing pages
  • Dropper chain: VBScript dropper → batch loader → compiled .NET executable → ScreenConnect agent installation
  • C2: Legitimate ScreenConnect relay infrastructure blended with Cloudflare tunnels (trycloudflare.com-style ephemeral tunnels), masking egress as trusted SaaS traffic
  • Staging: WsgiDAV (Python WebDAV) server on port 8080 — an increasingly common actor choice for lightweight payload hosting with directory listing and PUT support
  • Evasion: Windows Defender tampering, abuse of valid/abused code-signing certificates, cross-platform payload variants
  • Persistence: RMM agent installs as a service — persistence is inherent and blends with legitimate IT tooling

SockTz (CL-CRI-1131 and related LATAM cluster)

  • Distribution: Phishing campaigns crafted with AI assistance (self-hosted NextChat LLM instances)
  • Payload behavior: Deploys a SOCKS5 proxy implant, enrolling the victim into a proxy network usable for anonymized attacker traffic or resale
  • C2: DuckDNS dynamic hostnames for resilient, rapidly re-pointable resolution; IPv4 167.148.195.53
  • Techniques: Living-off-the-land binaries and scripts to minimize on-disk footprint
  • Targeting: Transportation and government in Mexico/Ecuador; finance in Brazil — Spanish/Portuguese lures

Teams Help Desk Vishing Cluster

  • Distribution: Direct Teams messages/calls impersonating IT support (often via compromised or externally federated tenants)
  • Execution: User is walked through launching a remote access tool or running a scripted payload
  • Post-compromise: Lateral movement tooling staged from the eight enumerated IPv4 servers

IOC Analysis

Indicator composition across pulses:

  • FileHash-SHA256 (9 shown): Droppers and .NET loaders from the ScreenConnect campaign plus SockTz stage payloads. Hashes are high-fidelity but short-lived — operators recompile frequently (evidenced by the .cs source artifact on staging). Push hashes to EDR blocklists but treat as point-in-time.
  • IPv4 (9 shown): 207.174.0.143 (WsgiDAV staging, port 8080), 167.148.195.53 (SockTz C2), and the eight Teams-campaign servers. Block at egress firewall/proxy; alert on any historical connections via NetFlow or firewall log lookback (30+ days).
  • Domains/hostnames (6 shown): crestmarkhq.com, blog.derrspecial-onlinedmin.live, and four DuckDNS hostnames. DuckDNS indicators warrant DNS-layer blocking and retroactive DNS log hunts — dynamic DNS resolution patterns (short TTLs, infrequent internal resolution) are themselves a detection signal.
  • URL (1 shown): http://207.189.11.170/Bin/working_payload.cs — direct-IP payload retrieval over HTTP. Any internal fetch of bare-IP URLs with code file extensions (.cs, .ps1, .bat, .vbs) is a strong generic detection.

Operationalization: Load indicators into your TIP (MISP/OpenCTI), sync to SIEM watchlists and EDR custom indicator lists (Defender TVM indicators, CrowdStrike IOC management), and enforce DNS sinkholing for DuckDNS hostnames at the resolver. Prioritize network IOCs over hashes — infrastructure is reused longer than binaries.

Detection Engineering

YAML
---
title: ScreenConnect RMM Agent Execution from Unapproved Path
description: Detects ScreenConnect client execution from non-standard directories or with suspicious parent processes, consistent with RMM abuse campaigns delivering ScreenConnect via VBScript/batch droppers.
author: Security Arsenal Threat Intelligence
status: experimental
logsource:
  category: process_creation
  product: windows
level: high
detection:
  selection_img:
    Image|endswith:
      - '\ScreenConnect.ClientService.exe'
      - '\ScreenConnect.WindowsClient.exe'
      - '\ScreenConnect.Client.exe'
  filter_approved:
    Image|startswith:
      - 'C:\Program Files\ScreenConnect Client'
      - 'C:\Program Files (x86)\ScreenConnect Client'
      - 'C:\Program Files\ConnectWise'
  condition: selection_img and not filter_approved
falsepositives:
  - Legitimate ScreenConnect deployments installed to custom paths
fields:
  - CommandLine
  - ParentImage
  - User
tags:
  - attack.t1219
  - attack.t1102
date: 2026/09/03
---
title: VBScript or Batch Dropper Spawning Script or .NET Payload Retrieval
description: Detects wscript/cscript or cmd batch execution spawning curl, certutil, bitsadmin, or powershell to retrieve payloads — matching the VBScript dropper / batch loader chain staging from WsgiDAV servers.
author: Security Arsenal Threat Intelligence
status: experimental
logsource:
  category: process_creation
  product: windows
level: high
detection:
  selection_parent:
    ParentImage|endswith:
      - '\wscript.exe'
      - '\cscript.exe'
      - '\cmd.exe'
  selection_child:
    Image|endswith:
      - '\curl.exe'
      - '\certutil.exe'
      - '\bitsadmin.exe'
      - '\powershell.exe'
      - '\pwsh.exe'
  selection_cmd:
    CommandLine|contains:
      - 'http://'
      - 'https://'
      - ':8080'
  condition: selection_parent and selection_child and selection_cmd
falsepositives:
  - Software deployment scripts run via batch wrappers
fields:
  - CommandLine
  - ParentCommandLine
tags:
  - attack.t1059.005
  - attack.t1105
  - attack.t1059.003
date: 2026/09/03
---
title: Outbound Connection to Dynamic DNS or RMM Campaign Infrastructure
description: Detects network connections to DuckDNS hostnames, identified SockTz C2, Teams-vishing staging IPs, or WsgiDAV staging infrastructure from the OTX pulses.
author: Security Arsenal Threat Intelligence
status: experimental
logsource:
  category: network_connection
  product: windows
level: critical
detection:
  selection_dns:
    DestinationHostname|endswith: '.duckdns.org'
  selection_ip:
    DestinationIp:
      - '207.174.0.143'
      - '207.189.11.170'
      - '167.148.195.53'
      - '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'
  selection_domain:
    DestinationHostname|contains:
      - 'crestmarkhq.com'
      - 'derrspecial-onlinedmin.live'
  condition: 1 of selection_*
falsepositives:
  - Rare legitimate DuckDNS usage by internal tooling; investigate per-environment
fields:
  - DestinationHostname
  - DestinationIp
  - DestinationPort
  - Image
tags:
  - attack.t1071.001
  - attack.t1568.002
  - attack.t1090
date: 2026/09/03
KQL — Microsoft Sentinel / Defender
// Security Arsenal — OTX Pulse Hunt: ScreenConnect RMM abuse, SockTz, Teams vishing infrastructure
// Hunts network connections and suspicious process chains across the last 14 days
let BadIPs = dynamic(["207.174.0.143","207.189.11.170","167.148.195.53","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 BadHosts = dynamic(["crestmarkhq.com","blog.derrspecial-onlinedmin.live","m-doxa-apodo.duckdns.org","m-doxa-geo.duckdns.org","m-doxa-intel.duckdns.org","m-doxa-vacunas.duckdns.org"]);
let NetworkHits = DeviceNetworkEvents
| where TimeGenerated > ago(14d)
| where RemoteIP in (BadIPs) or RemoteUrl has_any (BadHosts) or RemoteUrl endswith ".duckdns.org"
| project HitType="NetworkIOC", TimeGenerated, DeviceName, RemoteIP, RemoteUrl, RemotePort, InitiatingProcessFileName, InitiatingProcessCommandLine;
let DropperChain = DeviceProcessEvents
| where TimeGenerated > ago(14d)
| where InitiatingProcessFileName in~ ("wscript.exe","cscript.exe","cmd.exe","mshta.exe")
| where FileName in~ ("powershell.exe","curl.exe","certutil.exe","bitsadmin.exe")
| where ProcessCommandLine has_any ("http://","https://",":8080","screenconnect","duckdns")
| project HitType="DropperChain", TimeGenerated, DeviceName, InitiatingProcessFileName, FileName, ProcessCommandLine, InitiatingProcessCommandLine;
let RMMAnomaly = DeviceProcessEvents
| where TimeGenerated > ago(14d)
| where FileName has_any ("ScreenConnect","ConnectWise")
| where not (FolderPath startswith @"C:\Program Files")
| project HitType="RMMAnomaly", TimeGenerated, DeviceName, FileName, FolderPath, ProcessCommandLine, InitiatingProcessFileName;
union NetworkHits, DropperChain, RMMAnomaly
| sort by TimeGenerated desc
PowerShell
# Security Arsenal — OTX Pulse IOC Hunt (ScreenConnect abuse / SockTz / Teams vishing)
# Run elevated on endpoints; outputs findings to console and CSV
$badIPs = @("207.174.0.143","207.189.11.170","167.148.195.53","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")
$badHosts = @("crestmarkhq.com","derrspecial-onlinedmin.live","duckdns.org")
$findings = @()

# 1. Active and historical TCP connections to known-bad IPs
Get-NetTCPConnection -ErrorAction SilentlyContinue | Where-Object { $badIPs -contains $_.RemoteAddress } | ForEach-Object {
    $proc = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
    $findings += [PSCustomObject]@{Type="NetworkConnection"; Detail="$($_.LocalAddress):$($_.LocalPort) -> $($_.RemoteAddress):$($_.RemotePort) [$($_.State)] PID $($_.OwningProcess) $($proc.ProcessName)"}
}

# 2. DNS client cache for malicious / dynamic-DNS hostnames
Get-DnsClientCache -ErrorAction SilentlyContinue | Where-Object { $n=$_.Entry; ($badHosts | Where-Object { $n -like "*$_*" }) } | ForEach-Object {
    $findings += [PSCustomObject]@{Type="DNSCache"; Detail="$($_.Entry) -> $($_.Data)"}
}

# 3. ScreenConnect / RMM services and persistence outside approved paths
Get-CimInstance Win32_Service -ErrorAction SilentlyContinue | Where-Object { $_.Name -match "ScreenConnect|ConnectWise|cloudflared" } | ForEach-Object {
    $suspicious = $_.PathName -notmatch "^"?C:\Program Files"
    $findings += [PSCustomObject]@{Type="RMMService$(if($suspicious){'-SUSPICIOUS'})"; Detail="$($_.Name) | $($_.State) | $($_.PathName)"}
}

# 4. Run-key and scheduled task persistence referencing scripts, RMM, or tunnels
$runKeys = @("HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Run","HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Run")
foreach ($key in $runKeys) {
    Get-ItemProperty -Path $key -ErrorAction SilentlyContinue | ForEach-Object {
        $_.PSObject.Properties | Where-Object { $_.Value -match "screenconnect|cloudflared|duckdns|\.vbs|wscript|appdata" } | ForEach-Object {
            $findings += [PSCustomObject]@{Type="RunKey"; Detail="$key :: $($_.Name) = $($_.Value)"}
        }
    }
}
Get-ScheduledTask -ErrorAction SilentlyContinue | Where-Object { ($_.Actions.Execute -match "wscript|powershell|curl") -or ($_.Actions.Arguments -match "http|duckdns|screenconnect|cloudflared") } | ForEach-Object {
    $findings += [PSCustomObject]@{Type="ScheduledTask"; Detail="$($_.TaskName) | $($_.Actions.Execute) $($_.Actions.Arguments)"}
}

# 5. VBScript / batch dropper artifacts in user-writable temp locations
$dropPaths = @("$env:TEMP","$env:APPDATA","$env:LOCALAPPDATA","$env:PUBLIC")
foreach ($p in $dropPaths) {
    Get-ChildItem -Path $p -Recurse -Include *.vbs,*.bat,*.cs -ErrorAction SilentlyContinue | Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-30) } | ForEach-Object {
        $findings += [PSCustomObject]@{Type="DropperFile"; Detail="$($_.FullName) (modified $($_.LastWriteTime))"}
    }
}

if ($findings) { $findings | Format-Table -AutoSize; $findings | Export-Csv -Path ".\otx_hunt_$(Get-Date -Format 'yyyyMMdd_HHmm').csv" -NoTypeInformation } else { Write-Host "[+] No indicators of compromise found." }

Response Priorities

Immediate (0–4 hours):

  • Block all enumerated IPv4 addresses at the egress firewall and web proxy; sinkhole crestmarkhq.com, derrspecial-onlinedmin.live, and all listed DuckDNS hostnames at the DNS resolver
  • Push the SHA256 hashes to EDR blocklists and run a fleet-wide hash sweep
  • Execute the KQL hunt and PowerShell script against all endpoints; any host with connections to 207.174.0.143:8080 or 167.148.195.53 should be isolated pending triage
  • Alert on any ScreenConnect, ConnectWise, or cloudflared binary executing outside approved software inventory — remove unauthorized instances immediately

24 hours:

  • Because the Teams vishing and RMM campaigns grant operators interactive keyboard access, treat any confirmed compromise as a full identity compromise: force password resets and revoke active sessions/refresh tokens for all users on affected hosts
  • Audit Teams external access/federation logs for unsolicited inbound chats or calls from external tenants claiming to be IT support; review Entra ID sign-in logs for anomalous session activity following Teams contact
  • Audit VPN, proxy, and ZTNA logs for SOCKS5-style long-duration outbound sessions from endpoints (SockTz behavior), particularly in LATAM business units

1 week:

  • Implement an RMM allowlist policy: only pre-approved remote access tools may execute; block all others via AppLocker/WDAC or EDR custom rules — this single control neutralizes the dominant technique across all three pulses
  • Disable or strictly govern Teams external federation; restrict inbound chats to allowlisted partner domains and deploy user-facing guidance for verifying IT help desk contact
  • Enforce browser/proxy policy blocking bare-IP HTTP downloads and connections to dynamic DNS providers from corporate assets
  • For LATAM-facing organizations: add Spanish/Portuguese phishing simulations themed on government services and transportation logistics; brief finance teams on AI-generated lure quality (assume flawless language)
  • Restrict wscript.exe/cscript.exe execution via WDAC or attack surface reduction rules for standard users

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.