SecOraLens
CriticalAPT

ARTEX: 916 Exposed AI Pentest Consoles Mapped in the U.S.

SOCRadar·Source published ·1 min read

What happened?

ARTEX is an open-source, LLM-driven autonomous penetration-testing framework, and its web console is now deployed at scale on U.S. commercial hosting. Starting from internet-wide scanner telemetry, SOCRadar researchers merged and de-duplicated 1,295 U.S.-hosted candidate instances, re-validated each one, and confirmed 916 live ARTEX-family consoles in a snapshot taken on November 11, 2026. The software was built to help security teams test systems they own.

Key details

  • SOCRadar researchers identified 916 live ARTEX-family consoles in the U.S. from 1,295 candidate IPs scanned on November 11, 2026.
  • The vast majority of consoles, 896 out of 916, are served over plain HTTP without encryption.
  • Over half of the live consoles are concentrated in just 19 contiguous /24 blocks, primarily on AS54600 (PEG TECH).
  • A single self-signed certificate is reused across 202 hosts in nine /24 blocks, indicating a shared operator or golden image.
  • 231 U.S. ARTEX hosts also run a Sub2API AI API gateway on a second port, mostly within the PEG TECH super-blocks.
  • Trojanized Docker images on Docker Hub provide an unauthenticated root shell via a hidden verifyCaptcha() function in the login handler.
  • Public reporting found 62 consoles serving the backdoored build, with 26 located in the U.S., making operators themselves victims.

What is affected?

  • 916 confirmed live ARTEX-family consoles in the U.S. as of November 11, 2026.
  • Docker images tomicdd/artex and congdonglinux/artex identified as backdoored builds.

What should defenders look for?

  • Console title pattern ending with – 自主渝透测试控制台.
  • Current favicon hash -576220750 seen on 817 live hosts.
  • Default ports 8787 and 8790 used for the ARTEX console.
  • Shared self-signed certificate across 202 hosts in nine /24 blocks.
  • Sub2API AI API Gateway console running on a second port alongside ARTEX.
  • Build fingerprint d284c4c4797bf94e found on 661 hosts.

Summarised by SecOraLens from SOCRadar. Always read the original source before acting. How SecOraLens verifies advisories.

What to do next

For CISOs and SOC leads

Brief your board. Brief your team.

Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.