Sophos Details ARTEX Use in Intrusions and Offers Hunting Guidance

· Original article ↗

Summary

Sophos describes reported ARTEX use in intrusions, shares activity patterns and detection coverage, and recommends hunting indicators and steps to secure application identities. Microsoft attributes the ConnectWise Cloud Backup compromise to Storm-0940.

Key points

  • ARTEX is an open-source, Go-based multi-agent penetration-testing framework that can plan target activity, invoke offensive tools, and pursue multiple paths.
  • Sophos says multiple threat actors have used ARTEX since its public release in July 2026. Microsoft attributes the ConnectWise Cloud Backup compromise to Storm-0940, which it assesses as China-state aligned.
  • Reported campaigns used authentication material or compromised application credentials against cloud APIs and services, including Microsoft Graph.
  • Sophos observed customer activity consistent with ARTEX or other AI-assisted tooling, including webshell activity, SQL Server command execution, credential theft, and attempted lateral movement.
  • Sophos recommends hunting for application-added service principal credentials or role assignments, scripted-user-agent sign-ins, ARTEX-related temporary files, structured command markers, and bursts of repeated commands.
  • Recommended defenses include auditing Entra ID service principals and enterprise apps, reviewing credential and role changes since September 2026, applying Conditional Access where available, and automating containment for privileged access.

Article Details

Defense Focus
Detect and disrupt ARTEX-related and other AI-assisted offensive activity, especially misuse of application credentials, cloud role changes, suspicious command patterns, and webshell activity.
Detection Methods
  • Hunt for service principal credentials added or roles assigned by an application, and application sign-ins using scripted user agents.
  • On hosts, look for temporary tooling or output files matching i<intentID>[variant]_<purpose>.<ext>, especially files or paths beginning with artx under C:\Windows\Temp.
  • Look for structured execution-verification markers such as MARKER123 or ARTX123, particularly alongside rapid command sequences, repeated command variants, or output written to temporary files.
  • Review endpoint detections across initial access, server execution, credential theft and collection, lateral movement, tool transfer, webshells, and execution activity.
  • Hunt back to at least September 2026 for activity attributed by Microsoft to Storm-0940.
Data Sources
  • Microsoft Entra ID service principal and enterprise application audit events, including credential additions and role assignments
  • Application sign-in logs, including user-agent and authentication-failure information
  • Host endpoint telemetry, including command activity, temporary files, and file paths
  • Network-observable activity inspected by firewall and endpoint IPS signatures
Rule Types
  • Sophos Firewall and Endpoint IPS signatures for ARTEX-related network-observable behavior
  • Taegis XDR detection for application-added service principal credentials or roles, and scripted-user-agent sign-ins
  • Sophos Endpoint behavioral detections and Active Adversary Protection rules
  • File detections for the trojanized ARTEX Docker image and related detections
  • IP reputation blocking for IPs associated with publicly reported ARTEX use
Platforms
  • Microsoft Entra ID
  • Sophos Endpoint
  • Sophos Firewall
  • Taegis XDR
Defensive Actions
  • Audit service principals and enterprise applications in Microsoft Entra ID; remove unused third-party app consents and review credential additions and role assignments since September 2026.
  • Apply Conditional Access policies to workload identities where licensing allows, restricting application sign-ins to expected locations.
  • Alert on application sign-ins with scripted user agents and authentication-failure rates above normal baselines.
  • Automate rapid containment for attacks reaching privileged access, such as disabling a service principal or revoking its credentials, with analyst confirmation afterward.
  • Treat ARTEX copies obtained from unofficial mirrors or clones as untrusted.
  • Register authorized red-team frameworks, infrastructure, and tooling names with the SOC so legitimate activity can be distinguished.

MITRE ATT&CK

Threat Actors

Malware

Vendors

Products

Tools

Countries

Related Articles