The FBI has issued a public warning that threat actors are operationalizing ARTEX, an AI-powered penetration testing framework, to automate cyberattacks against organizations worldwide. This is not a theoretical risk: ARTEX has been tied to a recent ConnectWise supply-chain breach that cascaded into compromised Microsoft 365 customer environments. When a framework can autonomously plan, execute, and adapt attack chains — reconnaissance, exploitation, lateral movement, persistence — the dwell-time advantage defenders once had collapses. Every SOC and MSSP managing M365 tenants, remote-access tooling, or downstream customer environments should treat this as an active-threat hunting exercise, not a news blurb.
The core defensive problem is twofold. First, ARTEX dramatically lowers the operator skill floor: tasks that once required a seasoned red teamer — phishing lure generation, exploit selection, credential brute-forcing, C2 improvisation — are now orchestrated by the framework at machine speed. Second, the ConnectWise incident demonstrates the multiplier effect of supply-chain compromise: one breached MSP/RMM platform becomes a trusted conduit into dozens or hundreds of downstream Microsoft 365 tenants. If you run ConnectWise ScreenConnect/Automate, or your MSP does, assume your environment is in scope until proven otherwise.
Technical Analysis
What ARTEX Is and Why It Matters
ARTEX is an AI-driven offensive security framework that automates the traditional penetration-testing kill chain: target reconnaissance, vulnerability identification, payload and lure generation, exploitation, and post-exploitation tasking. In criminal hands, the same orchestration engine becomes an attack robot capable of running campaigns at scale without deep operator expertise. The FBI's assessment is that ARTEX is actively powering intrusions globally — this is confirmed in-the-wild usage, not a proof-of-concept.
From a defender's vantage, the observable characteristics of an AI-automated intrusion differ from human-paced attacks in ways you can hunt for:
- Compressed timelines: recon-to-exploitation measured in minutes, not days. Burst activity in logs is a signal.
- Breadth over depth: parallel testing of many endpoints, accounts, and exposed services simultaneously.
- Machine-generated phishing: high-volume, highly personalized lures with low typo rates and context-aware pretexts harvested from public sources.
- Scripted post-exploitation: rapid, sequential execution of discovery commands (
whoami,net,nltest,ipconfig, cloud token enumeration) immediately after initial access.
The ConnectWise Supply-Chain Vector
The reported ConnectWise breach follows a familiar but devastating pattern: attackers compromise a remote monitoring and management (RMM) platform or its update/authentication infrastructure, then ride the RMM's trusted agent and legitimate credentials into customer environments. Because RMM agents run with SYSTEM-level privileges and are explicitly allowlisted by most EDR policies, malicious commands pushed through the RMM control plane blend into administrative noise.
The downstream impact on Microsoft 365 tenants is the critical escalation. With SYSTEM access on an endpoint or a management server's stored credentials, attackers can:
- Harvest cached M365/OAuth tokens from endpoint token caches and browser credential stores.
- Register attacker-controlled devices or applications into Entra ID (Azure AD) to establish durable cloud persistence.
- Abuse legitimate RMM tooling to stage data exfiltration or deploy secondary payloads across every managed endpoint simultaneously.
Attack chain summary for defenders:
ConnectWise platform compromise
→ trusted RMM agent issues attacker commands (SYSTEM context)
→ endpoint discovery + credential/token theft
→ Entra ID app registration / device join for persistence
→ mailbox access, data theft, lateral spread to downstream tenants
Exploitation Status
- Active exploitation: Confirmed. The FBI warning reflects observed, ongoing campaigns, including the ConnectWise-linked M365 compromises.
- CVEs: No CVE identifiers are named in the public reporting for this campaign. Do not anchor your response on patching a single CVE — the risk here is tradecraft (AI-automated intrusion, RMM trust abuse, token theft), not one missing patch. That said, RMM platforms must be on current vendor builds as a baseline.
- CISA KEV: Not specifically cited in the reporting; monitor CISA KEV and FBI/CISA joint advisories for follow-on technical indicators.
Detection & Response
The detections below target the behaviors this campaign exhibits: RMM control-plane abuse, scripted post-exploitation bursts, M365 token/credential theft, and Entra ID persistence. These are high-fidelity hunts, not generic analytics.
Sigma Rules
---
title: RMM Agent Spawning Discovery or Recon Commands
description: Detects ConnectWise ScreenConnect/Automate agents spawning rapid discovery commands consistent with AI-automated post-exploitation via a compromised RMM control plane.
id: 9b2c4f61-3a7e-4d58-b2c1-8f6e5d4a3b21
status: experimental
references:
- https://www.bleepingcomputer.com/news/security/fbi-warns-artex-ai-hacking-tool-is-powering-global-cyberattacks/
- https://attack.mitre.org/techniques/T1219/
- https://attack.mitre.org/techniques/T1033/
author: Security Arsenal
date: 2026/04/06
tags:
- attack.discovery
- attack.t1033
- attack.t1219
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith:
- '\ScreenConnect.ClientService.exe'
- '\ScreenConnect.WindowsClient.exe'
- '\LabTech.Service.exe'
- '\LTTray.exe'
selection_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\whoami.exe'
- '\net.exe'
- '\nltest.exe'
- '\ipconfig.exe'
- '\systeminfo.exe'
condition: selection_parent and selection_child
falsepositives:
- Legitimate MSP scripting via RMM — baseline against your MSP's known maintenance windows and script hashes
level: high
---
title: Suspicious Access to Microsoft 365 Token and Credential Caches
description: Detects non-browser, non-Office processes accessing Microsoft Identity token caches and credential stores, consistent with token theft following RMM-based SYSTEM compromise.
id: 4e8d1a72-6c5b-4f39-a1d7-2b9c8e6f5a43
status: experimental
references:
- https://www.bleepingcomputer.com/news/security/fbi-warns-artex-ai-hacking-tool-is-powering-global-cyberattacks/
- https://attack.mitre.org/techniques/T1528/
- https://attack.mitre.org/techniques/T1555/
author: Security Arsenal
date: 2026/04/06
tags:
- attack.credential_access
- attack.t1528
- attack.t1555
logsource:
category: file_event
product: windows
detection:
selection_paths:
TargetFilename|contains:
- '\Microsoft\IdentityCache\'
- '\Microsoft\TokenBroker\'
- '\Microsoft\Credentials\'
- '\Microsoft\Protect\'
- '\Google\Chrome\User Data\Default\Cookies'
- '\Google\Chrome\User Data\Default\Login Data'
filter_legit:
Image|endswith:
- '\msedge.exe'
- '\chrome.exe'
- '\Teams.exe'
- '\OUTLOOK.EXE'
- '\winword.exe'
- '\explorer.exe'
- '\MsMpEng.exe'
- '\svchost.exe'
condition: selection_paths and not filter_legit
falsepositives:
- Backup agents and EDR scanners — exclude by known process path after triage
level: high
---
title: Automated Phishing Infrastructure - Burst Authentication Anomaly Precursor
id: 7c1f3e58-2d9a-4b47-9e6c-5a4b8d3f2e10
status: experimental
description: Detects rapid sequential cloud enumeration commands on an endpoint, a hallmark of AI-orchestrated post-compromise tooling executing discovery at machine speed.
references:
- https://www.bleepingcomputer.com/news/security/fbi-warns-artex-ai-hacking-tool-is-powering-global-cyberattacks/
- https://attack.mitre.org/techniques/T1087/
author: Security Arsenal
date: 2026/04/06
tags:
- attack.discovery
- attack.t1087
- attack.t1069
logsource:
category: process_creation
product: windows
detection:
selection:
CommandLine|contains:
- 'net group "Domain Admins"'
- 'net localgroup administrators'
- 'nltest /dclist'
- 'nltest /domain_trusts'
- 'dsquery computer'
- 'dsquery user'
filter_admin:
ParentImage|endswith:
- '\sccm\'
- '\pdqdeploy'
condition: selection and not filter_admin
falsepositives:
- Sysadmin enumeration during audits — correlate with account and time-of-day context
level: medium
KQL Hunt — Sentinel / Defender
Hunt the three highest-value surfaces: RMM-spawned scripting, token-cache access, and anomalous Entra ID application registrations (persistence).
// 1. RMM control-plane abuse: ScreenConnect/Automate spawning script interpreters or discovery tools
DeviceProcessEvents
| where TimeGenerated > ago(7d)
| where InitiatingProcessFileName has_any ("ScreenConnect", "LabTech", "LTTray")
| where FileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "whoami.exe", "net.exe", "nltest.exe", "rundll32.exe", "wscript.exe", "cscript.exe", "mshta.exe")
| project TimeGenerated, DeviceName, AccountName, InitiatingProcessFileName, FileName, ProcessCommandLine, SHA256
| order by TimeGenerated desc;
// 2. Token/credential cache access by unexpected processes (M365 token theft)
DeviceFileEvents
| where TimeGenerated > ago(7d)
| where FolderPath has_any ("IdentityCache", "TokenBroker", @"Microsoft\Credentials", @"Microsoft\Protect")
| where not(InitiatingProcessFileName in~ ("msedge.exe", "chrome.exe", "Teams.exe", "OUTLOOK.EXE", "explorer.exe", "svchost.exe", "MsMpEng.exe"))
| summarize AccessCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, FolderPath
| order by AccessCount desc;
// 3. Entra ID persistence: new app registrations / service principals / device joins during suspected window
AuditLog
| where TimeGenerated > ago(14d)
| where OperationName has_any ("Add application", "Add service principal", "Add app role assignment", "Consent to application", "Add device")
| extend Actor = tostring(parse_json(InitiatedBy).user.userPrincipalName)
| extend TargetName = tostring(TargetResources[0].displayName)
| project TimeGenerated, OperationName, Actor, TargetName, Result, IPAddress
| order by TimeGenerated desc;
Tune query 2 against your environment's backup agents and EDR processes first — everything else should be triaged as suspicious until cleared.
Velociraptor VQL Hunt
-- Hunt for RMM agent child processes executing discovery/scripting at machine speed (ARTEX-style automation)
SELECT Pid,
Ppid,
Name,
Exe,
CommandLine,
Username,
CreateTime,
dict(Pid=Ppid) AS _Parent,
(SELECT Name, Exe FROM pslist(pid=Ppid)) AS ParentInfo
FROM pslist()
WHERE (
ParentInfo[0].Exe =~ '(?i)ScreenConnect|LabTech|LTTray|Automate'
AND Name =~ '(?i)cmd|powershell|pwsh|whoami|net\.exe|nltest|mshta|rundll32|wscript|cscript'
)
OR (
CommandLine =~ '(?i)net group "domain admins"|nltest /dclist|nltest /domain_trusts|dsquery'
)
ORDER BY CreateTime DESC
For a wider sweep, pair this with a glob hunt over RMM directories for recently written unexpected binaries: SELECT FullPath, Mtime, Size FROM glob(globs='C:\\Program Files*\\**ScreenConnect**\\*.exe') ORDER BY Mtime DESC.
Remediation & Hardening Script
Run this PowerShell (as Administrator, from your management tooling) to audit RMM exposure, token-cache access controls, and surface indicators on a suspect endpoint. It is a triage/hardening aid — not a substitute for full IR.
# ARTEX / ConnectWise supply-chain triage & hardening script - run elevated
$report = @()
# 1. Identify installed RMM agents and their versions
$rmmPaths = @(
"HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*",
"HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*"
)
$installed = Get-ItemProperty $rmmPaths -ErrorAction SilentlyContinue |
Where-Object { $_.DisplayName -match "ScreenConnect|ConnectWise|LabTech|Automate" } |
Select-Object DisplayName, DisplayVersion, InstallDate
$report += "=== Installed RMM Products ==="
$report += ($installed | Format-Table | Out-String)
# 2. Flag ScreenConnect/Automate child processes spawned in last 24h from Security log
$report += "=== Suspicious RMM Child Processes (24h, if Sysmon/4688 enabled) ==="
$procs = Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4688; StartTime=(Get-Date).AddDays(-1)} -ErrorAction SilentlyContinue |
Where-Object { $_.Message -match "ScreenConnect|LabTech" -and $_.Message -match "cmd.exe|powershell|whoami|nltest" } |
Select-Object TimeCreated, Message -First 25
$report += ($procs | Format-List | Out-String)
# 3. Audit ACLs on M365 token caches for unexpected principals
$report += "=== Token Cache ACLs ==="
$cachePaths = @("$env:LOCALAPPDATA\Microsoft\IdentityCache", "$env:LOCALAPPDATA\Microsoft\TokenBroker")
foreach ($p in $cachePaths) {
if (Test-Path $p) {
$acl = Get-Acl $p
$report += "$p : " + (($acl.Access | Select-Object IdentityReference, FileSystemRights | Format-Table | Out-String))
}
}
# 4. Harden: block outbound ScreenConnect to non-approved hosts via firewall (adjust CIDR to your MSP)
New-NetFirewallRule -DisplayName "Block Unmanaged ScreenConnect Outbound" `
-Direction Outbound -Program "C:\Program Files*\ScreenConnect*\*.exe" `
-Action Block -ErrorAction SilentlyContinue | Out-Null
$report += "Firewall block rule created (review and scope to approved RMM IPs before enforcement)."
# 5. Export findings
$report | Out-File "$env:TEMP\artex_triage_$(Get-Date -Format yyyyMMdd_HHmm).txt"
Write-Output "Triage report written to $env:TEMP - review, then scope the firewall rule to your MSP's documented IPs only."
Important: the firewall rule in step 4 is a starting point. Enforcing it broadly will break your MSP's legitimate access — scope it to allow only your provider's documented RMM infrastructure before any enforcement action.
Remediation
Prioritized actions, in order:
-
Engage your MSP/RMM vendor immediately. Demand written confirmation of their patch posture, whether they were in the blast radius of the reported ConnectWise compromise, and what authentication/integrity controls protect the control plane (signed scripts, certificate pinning, IP allowlisting, MFA on technician consoles). If answers are vague, treat the channel as untrusted.
-
Patch RMM components to current vendor builds. Apply the latest ConnectWise ScreenConnect/Automate releases per ConnectWise security advisories at https://www.connectwise.com/company/trust/security-bulletins — even though no CVE is cited in this campaign, RMM platforms are high-value targets and currency is non-negotiable.
-
Constrain the RMM control plane. Restrict inbound/outbound RMM traffic to documented vendor IPs, enforce MFA and conditional access on all technician accounts, disable or tightly scope unattended access, and alert on any RMM session originating outside expected geographies or hours.
-
Hunt for Entra ID persistence now. Review all app registrations, service principals, consent grants, and device joins over the past 30+ days. Revoke anything you cannot attribute. Force token revocation (
Revoke-AzureADUserAllRefreshToken/ GraphrevokeSignInSessions) for any account touched by a suspect endpoint, and reset credentials assuming theft. -
Assume token theft on impacted endpoints. For any host where RMM abuse is suspected, reimage rather than clean — SYSTEM-level access via a trusted agent defeats incremental eradication. Rotate all secrets that ever transited those hosts.
-
Tune your detections for machine-speed attacks. ARTEX-style automation produces burst telemetry. Build analytics around velocity: N distinct discovery commands within 60 seconds, N distinct hosts touched per session, parallel authentication attempts. Human-paced baselines will miss it.
-
Prepare for AI-generated phishing. Because ARTEX industrializes lure creation, refresh user reporting workflows, tighten mail flow rules for lookalike domains and newly registered senders, and verify that phishing-resistant MFA (FIDO2/passkeys) is deployed for privileged and MSP-facing accounts — push fatigue and TOTP interception are still being harvested at scale.
-
Monitor for follow-on indicators. Track the FBI/CISA advisory channels and BleepingComputer coverage for IOC releases tied to this campaign, and subscribe to CISA KEV for any CVEs that emerge from the ConnectWise investigation. Feed indicators into your SIEM/EDR blocklists the day they drop.
Category
soc-mdr
Related Resources
Security Arsenal Managed SOC Services AlertMonitor Platform Book a SOC Assessment soc-mdr Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.