SOC Prime Outlines Detection and Hunting for ARTEX and PHP2Shell

· Original article ↗

Summary

The article outlines behavior-based detection and mitigation for ARTEX, an LLM-driven pentesting framework reportedly used in attacks, and provides PHP2Shell hunting guidance for CVE-2026-109618 and CVE-2026-109619.

Key points

  • ARTEX is described as a Go framework whose Planner and Worker agents use LLM endpoints to automate reconnaissance, probing, and exploitation. Its author disowned malicious use and removed the repository, but forks and rebrands remain in circulation.
  • Censys counted 1,465 exposed ARTEX consoles in early November, most using default port 8787.
  • The article recommends behavior-based detection across telemetry, including web-server error spikes and sequential probes, identity login and account-recovery anomalies, and web services spawning shells or scanning tools.
  • Additional signals include Azure write-then-delete blob activity, AWS EC2 dry-run permission checks, and network egress to LLM resellers or self-hosted proxies.
  • Mandiant and GTIG recorded 27 events in 23 seconds and automated error correction used to land webshells, according to the article. It also lists reported campaigns involving financial, IT, software, and Japanese organizations.
  • PHP2Shell CVE-2026-109618 and CVE-2026-109619 are described as pre-authentication RCE chains affecting PHP 5.4.0 through 8.5.11; PHP shipped fixes on October 21, 2026.
  • For PHP2Shell, the article recommends hunting for upload-progress session fields, follow-up file-inclusion requests, canaries, and PHP workers spawning shells or download tools; it advises patching, upgrading end-of-life branches, and disabling upload progress where unnecessary.

Article Details

Defense Focus
Detect ARTEX-style automated reconnaissance and exploitation through correlated web, identity, endpoint/Linux, cloud, and network behavior rather than tool names.
Detection Methods
  • Correlate 40x response spikes from a single IP with path traversal, file inclusion, OS command injection, or scripted files dropped into web directories.
  • Look for a request to /swagger/?format=openapi followed immediately by a random nonexistent URI.
  • Alert on bursts of failed logins or access denials, password spraying, and account-recovery workflow abuse.
  • Identify web-service or PHP worker processes spawning shells, curl, or wget; investigate unexpected nmap, curl, or wget parent processes, SSH known_hosts discovery, and netcat paired with RAT binaries.
  • Hunt for multipart POST requests containing PHP_SESSION_UPLOAD_PROGRESS with attacker-chosen session IDs, followed by file-inclusion requests for sess_ files in PHP session directories.
  • Detect inert PHP canaries and unique output markers used to confirm code evaluation.
  • Review cloud audit events for Azure write-then-delete activity involving throwaway blobs and AWS EC2 calls using --dry-run to test IAM permissions.
  • Look for HTTP C2 to direct IP addresses on uncommon ports and egress to LLM resellers or self-hosted proxies.
Data Sources
  • Web server request and response logs
  • Identity-provider authentication and account-recovery logs
  • Endpoint and Linux process telemetry
  • PHP application and session-upload request logs
  • Azure and AWS cloud audit/API logs
  • Network egress and HTTP telemetry
Rule Types
  • Sigma rules
  • AI rules
Platforms
  • Web servers
  • Linux
  • Okta
  • Entra ID
  • Cognito
  • Azure
  • AWS
Defensive Actions
  • Patch PHP2Shell vulnerabilities CVE-2026-109618 and CVE-2026-109619; upgrade end-of-life PHP branches and disable upload progress tracking where applications do not need it.
  • Rate-limit by account, session, and API key rather than by IP alone.
  • Enforce API authorization server-side and issue short-lived credentials.
  • Harden identity-provider login and account-recovery flows.
  • Deploy decoys and tarpits, and validate detection coverage with simulation scripts.

Indicators of compromise

TypeIndicatorContext
DOMAINxcai[.]proLLM reseller identified by CrowdStrike and the article as an ARTEX-related IOC.
IPV4144[.]172[.]64[.]60Storm-0940 infrastructure identified by Microsoft and the article as an IOC.
IPV438[.]244[.]50[.]120ARTEX host identified by the article as an IOC to load for detection.

MITRE ATT&CK

CVE

Threat Actors

Malware

Products

Tools

Countries

Industries

Related Articles