Censys found 1,465 internet-facing hosts running the console of ARTEX, an open source framework of AI hacking tools, as of November 4, 2026. After setting aside two blocks of identically configured servers, Censys counts about 815 distinct ARTEX deployments, and 32 hosts were serving open directories that exposed implants, exploits and stagers.
Censys Counted 1,465 Exposed ARTEX AI Hacking Tool Consoles
Censys, which scans the internet for exposed and vulnerable systems, published the count on November 5, 2026 in a report by principal security researcher Silas Cutler. It identifies an ARTEX console by its page title together with the Next.js assets the console loads. About 650 of the hosts sit with two hosting providers in uniform layouts: 493 at PEG Tech (AS54600) and 157 at Yancy Limited (AS138415). Censys reads that uniformity as a provisioning template repeated across many addresses, which is why it puts the number of real deployments near 815. The largest share of hosts is in the United States (726), followed by Hong Kong (387) and China (177), and the most common console port is 8787, the ARTEX default. The console has no need to face the public internet, so Censys expects the total number of ARTEX installations to be higher than what it can see. It also says some of the exposed hosts are likely run by authorized testers.
ARTEX Is an Autonomous Attack Agent Framework Already Tied to Two Campaigns
A developer known as Autumn-27 published ARTEX on GitHub on July 26, 2026 under the AGPL-3.0 license. It is written in Go with a Next.js web console and a PostgreSQL backend. A user sets a task with a scope and a goal. A planner agent breaks the goal into attack intents, worker agents pick those up and run tools such as nmap, and the loop continues until the goal is met. It works with Anthropic, OpenAI or any OpenAI-compatible model endpoint. On October 7, CrowdStrike reported that an actor using ARTEX breached systems at two South Korean financial institutions. On October 21, Microsoft said China-aligned Storm-0940 used ARTEX in the ConnectWise supply-chain compromise, attempting sign-ins to more than 2,250 tenants. After the CrowdStrike report, Autumn-27 said they had no part in the attacks and that ARTEX would go closed source. The repository is gone, though Censys says archived copies and rebrands such as ScopeWeaver are still in circulation.
Open Directories on ARTEX Hosts Exposed the Attackers’ Own Toolkits
CrowdStrike traced the South Korean campaign partly because the operator left an open directory on the ARTEX server, exposing a .claude folder, prompts, session histories and ARTEX configuration files. Censys scan history shows open directories on that same server from August 18, 2026, seven weeks before CrowdStrike published. The mistake is common. While writing the report, Censys saw 32 open directories on other ARTEX hosts. One held a Windows lateral-movement kit. Another held a public exploit for the sudo flaw CVE-2021-3156. Others exposed Linux beacon implants, a compiled Windows stager, a MITM root CA private key, and one operator’s entire home directory, including .ssh and .bash_history. Most stayed up for hours or a couple of days. Between November 3 and November 5, 10 closed and 15 new ones appeared, and Censys keeps the file listings in its scan history after they disappear.
LLM Gateways Running Beside ARTEX Give Defenders a Signal to Hunt
Of the 1,465 ARTEX hosts, 155 (10.6%) also run at least one other threat that Censys detects. The most common companion is another AI attack framework: CyberStrikeAI shares 70 hosts with ARTEX, and PentAGI and HexStrike AI also appear. A smaller set pairs ARTEX with conventional command-and-control tools, including Cobalt Strike, Vshell and Adaptix C2. Forty-three ARTEX hosts run self-hosted LLM gateway or reseller software, mainly CLIProxyAPI (19 hosts) and New API (18 hosts). The actor in CrowdStrike’s report bought DeepSeek model access through a reseller. Censys tells defenders that unfamiliar LLM proxies and resellers appearing in egress logs deserve investigation.
Why This Matters for Engineering Leadership
An agent console is an administrative interface for a system that acts on its own, and the ARTEX numbers show its operators exposing it the way teams have exposed databases and dashboards for years. Hundreds of consoles face the internet with no technical reason to, and the directories beside them leak prompts, session histories and tooling. If your security team or a pentest vendor runs an autonomous testing framework, ask where its console lives and who can reach it. Put it behind your VPN or single sign-on and add it to the asset inventory. Treat its working files as sensitive, because a test agent’s session history is a map of your weaknesses. On the defensive side, Censys’s guidance is concrete enough to act on this week: add the ARTEX default port and the named LLM proxy software to your detection rules, and review outbound traffic to model resellers your organization does not use. TechCrunch’s Zack Whittaker notes that many ARTEX attacks relied on weak or known passwords and missing multi-factor authentication. The agent made those old gaps faster to find, so closing them still comes first.
FAQ
What is ARTEX?
ARTEX is an open source autonomous penetration testing framework released on GitHub on July 26, 2026. LLM-driven agents in it plan and run attack steps toward a goal with little human input.
How many ARTEX consoles are exposed to the internet?
Censys counted 1,465 hosts running an exposed ARTEX console as of November 4, 2026. Excluding two blocks of identically configured hosting leaves about 815 distinct deployments.
Is everyone running ARTEX an attacker?
No. Censys says some exposed hosts are likely run by authorized testers. CrowdStrike and Microsoft have tied ARTEX to campaigns against South Korean finance firms and ConnectWise customers.
What did the open directories on ARTEX hosts expose?
Censys found 32 open directories exposing implants, stagers, exploit code, a Windows lateral-movement kit, a MITM root CA private key and one operator’s entire home directory.
How can defenders hunt for ARTEX activity?
Censys points to ARTEX consoles on default port 8787, co-located Vshell or FRP listeners, and unfamiliar LLM proxies such as CLIProxyAPI or New API showing up in egress logs.
Is ARTEX still available?
Its developer said in October 2026 that ARTEX would go closed source, and the GitHub repository is down. Censys says archived copies and rebrands such as ScopeWeaver still circulate.
